Capitalize file extensions

Quick answer

Be consistent: match the actual filename when you're working with files (because some systems are case-sensitive), and pick one readable style for prose. For everyday writing, lowercase extensions like .pdf or .docx are common; for technical accuracy, use the exact case the file uses on disk.

Core explanation: what the extension does and why case matters

A file extension is the letters after the last period in a filename (for example, report.pdf → extension: pdf). The extension signals file type to users and programs. Whether you must match its case depends on two things: the system and your audience.

• System behavior: Many Windows and macOS setups are case-insensitive but preserve case; Linux and some servers are case-sensitive. On a case-sensitive system, report.PDF is a different filename from report.pdf.
• Software expectations: Scripts, build tools, and web servers may require exact matching. A link or import that uses the wrong case can fail in deployment even if it worked locally.
• Prose style: In running text you're describing a format (PDF, JPEG) rather than naming a specific file; choose a clear, consistent style. Many writers use lowercase with or without the dot (pdf or .pdf), while others write the common uppercase acronym (PDF).

When capitalization actually matters

Capitals matter for technical correctness and for readers' clarity. Use the exact case for:

• file references inside code, scripts, configuration files, or documentation that users will copy and paste;
• filenames on case-sensitive environments (Linux servers, some CI systems, Docker images, etc.);
• anywhere a mismatch could break a path, import, or automated workflow.

For general prose-emails, manuals, or help text-choose a readable convention and apply it consistently across the document.

Real usage: examples and common consequences

Three practical situations show why you should care.

• Development - A build script imports module.js but the file on disk is Module.js. On a Linux CI server the import fails; on a developer's mac it may pass, hiding the bug.
• Web deployment - Your HTML links to /images/logo.PNG while the server has logo.png. The image shows locally but 404s in production.
• Documentation - In user docs, writing Open the file report.PDF is fine if that is the actual name; otherwise use a consistent style like report.pdf or refer to the format by its acronym: open the PDF.

Examples you can copy: wrong → right (6 pairs + categorized examples)

These pairs show common mistakes and straightforward fixes.

• Wrong: Upload the file named budget.XLSX.
• Right: Upload the file named budget.xlsx.
• Wrong: Link to /assets/photo.JPG - image missing on server.
• Right: Link to /assets/photo.jpg.
• Wrong: Run start-Server.SH on the Linux host.
• Right: Run start-server.sh.

Grouped by context (work, school, casual):

• Work - Wrong: Please open Q2_Report.DOCX.
  Right: Please open Q2_report.docx.
• Work - Wrong: Upload invoice.PDF to the portal.
  Right: Upload invoice.pdf.
• Work - Wrong: The build imports Utils.JS.
  Right: The build imports utils.js.
• School - Wrong: Submit Essay.DOC.
  Right: Submit essay.doc.
• School - Wrong: Turn in presentation.PPTX.
  Right: Turn in presentation.pptx.
• School - Wrong: Attach references.BIB.
  Right: Attach references.bib.
• Casual - Wrong: I sent you vacation.JPG.
  Right: I sent you vacation.jpg.
• Casual - Wrong: Save it as song.MP3.
  Right: Save it as song.mp3.
• Casual - Wrong: Rename to recipe.TXT.
  Right: Rename to recipe.txt.

How to fix your own sentence and filenames (rewrite help)

Follow these quick steps whenever you edit filenames or mention extensions in text.

• Step 1: If you mean a specific file, copy the exact filename from the file system.
• Step 2: If you mean the format or type in prose, pick one style (lowercase with dot, lowercase without dot, or uppercase acronym) and stick to it across the document.
• Step 3: Run a quick search for variations and normalize them in bulk.
• Step 4: Test links and scripts on a case-sensitive environment if your deployment may be case-sensitive.

Quick rewrite examples you can paste:

• Original: Please open Draft.DOCX for review.
  Rewrite: Please open draft.docx for review.
• Original: The image located at /img/Banner.PNG fails.
  Rewrite: The image located at /img/banner.png works on the server.
• Original: Run the install script Install.SH.
  Rewrite: Run the install script install.sh.

A simple memory trick

Think: "match disk, then match prose." If you're naming a real file - match the disk exactly. If you're writing about the format - pick one readable convention and apply it everywhere.

• Disk-first rule for technical work.
• Style-first rule for user-facing text and documentation.
• When unsure, search your document for variations and normalize them.

Similar mistakes to watch for

Fixing extension case is often the first step. Watch for related issues that cause the same problems.

• Filename capitalization - Some systems treat Readme.md and README.md as different files.
• Extra periods - file.name.pdf vs file.pdf can confuse scripts that split on the first or last period.
• Hyphen and underscore differences - data-set.csv vs data_set.csv are different names.
• Pluralization and versioning - report_v1.pdf vs reports_v1.pdf are distinct filenames.

FAQ

Should file extensions be capitalized in regular writing?

Not necessary. For most prose, choose a clear convention (commonly lowercase) and remain consistent. For precise references to an actual file, use the filename's exact case.

Will changing case break anything?

Changing only the case can break links and scripts on case-sensitive systems. Always confirm the exact filename on disk before committing changes that matter to builds or deployment.

Is there a universal style rule?

No universal rule-style guides differ. The practical rules are consistency in documentation and exact matching when interacting with files or systems.

How do servers and browsers treat extension case?

Web servers and hosting environments can be case-sensitive. Browsers request the path you give; if the server expects a different case, you'll get a 404 error.

Should I change existing files to a single case?

If you can safely standardize filenames (and update links and references), it reduces future errors. Test on a case-sensitive system before deploying changes.

Check filenames and prose before you send

Quick checklist: did you copy actual filenames when required, keep a consistent style in documentation, and test links on a case-sensitive environment if deployment may be affected? A short pass with those three checks prevents most extension-related problems.