Formatting File Names in Technical Documentation records the relevant Microsoft Style Guide convention while keeping it explicitly house-style scoped rather than presenting it as a universal grammar rule.
ReviewedEvidence2 sourcesSectionWriting & Style
Quick answer
Use title-style capitalization for ordinary file-name references; internal capitals are acceptable for readability, and switch to code style when the name is shown in code syntax.
Key details
Core IssueMicrosoft style uses title-style capitalization for file names, allows internal capitals for readability, and applies code style when the file name appears as code syntax.
RegisterMicrosoft technical and professional documentation
Important caveats
Scope Boundary
The convention is Microsoft technical style; when documenting a real file whose exact casing matters, reproduce the actual file name rather than normalizing it.
Further guidance
Content
Use title-style capitalization for ordinary file-name references; internal capitals are acceptable for readability, and switch to code style when the name is shown in code syntax.
Purpose
Keep literal file names recognizable while distinguishing prose references from executable or code-syntax contexts.
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
Formatting Database Names in Technical Documentation records the relevant Microsoft Style Guide convention while keeping it explicitly house-style scoped rather than presenting it as a universal grammar rule.
Formatting Event Names in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Capitalizing Product Names in Technical Documentation records the relevant Microsoft Style Guide convention while keeping it explicitly house-style scoped rather than presenting it as a universal grammar rule.
Formatting AI Prompts in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Attributes in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Classes in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Code Keywords in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Code Samples in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it scoped to technical instructions rather than presenting it as a universal grammar rule.
