Turn a project title into a Windows-safe filename without losing the extension

Show the extension and rename a copy first

A Windows-safe filename starts with a recoverable test: copy one representative file into a small test folder, display its real extension, and rename only that copy. This separates a naming decision from the risk of losing track of the original file type or applying a mistake across a whole project folder.

This workflow was checked on 2026-08-15 against Microsoft Support guidance for Windows 11 and Windows 10. Open File Explorer and use View > Show > File name extensions. A filename such as Client Review Notes.docx has a base name, Client Review Notes, and an extension, .docx, separated by the last period. Keep .docx visible before editing anything.

If an organization-managed or updated File Explorer shows different toolbar wording, stop and find the equivalent setting that displays extensions. Do not guess a hidden ending. Microsoft explains that changing an extension changes the name only; it does not convert the file. Renaming report.docx to report.pdf therefore does not create a PDF and can make the renamed file confusing to open.

For example, copy Launch brief: North/West review.docx into a folder named filename-test. Record the original name, then plan to replace only the base. Keep the source document untouched until the renamed copy opens in the expected application and passes a content check.

Generate a consistent base without treating it as approval

Use the Slug Generator to turn a long project title into a compact candidate base. The tool replaces punctuation with a dash or underscore, can lowercase the result, can remove a fixed set of common English stopwords, and lets you set a maximum result length from 10 to 200 characters. Unicode letters and numbers remain in the candidate.

Paste Launch brief: North/West review into the tool, choose a dash, and copy the proposed base. A result similar to launch-brief-north-west-review is easier to scan than the punctuation-heavy title. Reattach the unchanged .docx extension yourself to form launch-brief-north-west-review.docx, then apply that name only to the test copy in File Explorer.

The tool produces text; it does not inspect a folder or rename a file. It also does not identify the existing extension, detect a duplicate, calculate the full path, or determine whether a reserved Windows device name has been produced. The maximum-length control applies only to the generated base, not to its parent folders or the destination system.

Keep stopword removal off when a small word carries meaning in your naming policy. Statement of Work and Statement Work may not mean the same thing to a reviewer. Lowercase is also a style choice, not a Windows requirement. Choose settings that help people identify the document, then perform the Windows checks separately.

Check reserved characters, endings, and device names

Microsoft Learn lists general Win32 naming conventions, while noting that individual file systems can add restrictions. Before accepting a candidate, check the visible full name against the following rules:

• Remove <, >, :, ", /, \, |, ?, and * from the base name. Use a meaningful dash or short word where simple deletion would merge two ideas.
• Do not use CON, PRN, AUX, or NUL as the base. Avoid COM1 through COM9 and LPT1 through LPT9 as well. Adding an extension does not rescue a reserved name such as NUL.txt.
• Do not end the base with a space or period. A trailing character can be visually easy to miss and is not accepted by the normal Windows shell interface.
• Do not depend on capitalization alone to distinguish two files. Windows applications should not assume case sensitivity, so Review.docx and review.docx are a collision risk rather than a useful version scheme.
• Look for an existing file with the proposed full name before renaming the copy. Add an informative date, revision, client code, or document state when two valid files would otherwise collide.

The slug generator removes ordinary punctuation from its output, which helps with the reserved-character check. It does not block reserved words. An input of CON can still produce con, so the human review remains necessary.

Keep an old-to-new map before changing a batch

A filename is part of a document workflow, not merely a label. Before renaming more than the test copy, create a map with the original full name, proposed full name, reason, and review result. The Online Notepad can hold a plain-text working list, but it does not back up or alter files; store the approved map in the project’s normal record location.

A small map might say Client Review Notes.docx → client-review-notes-2026-08-15.docx → opens correctly. Include enough context to reverse a mistaken decision. Avoid a list that records only new names, because it cannot show which original file supplied the content.

This article deliberately uses File Explorer rather than a batch command. If a later approved workflow uses PowerShell, create a complete backup or isolated test folder first and run the proposed rename with -WhatIf before any real change. A preview helps find collisions, but it does not replace a backup or a content review.

Verify the name in the real destination

Open the renamed copy and confirm that the expected application recognizes it, the content belongs to the recorded original, and the visible extension is unchanged. Close and reopen it rather than relying on an already open window. Then place a non-sensitive test copy in the actual destination, such as the network share, removable drive, archive, upload folder, or sync location used by the project.

A name accepted on one Windows disk can still fail elsewhere because the target file system or service has additional rules. Watch for a collision, truncation, sync warning, rejected upload, or a path that becomes too long when parent folders are included. If the destination changes the name, record what happened and revise the candidate before applying it to more files.

After the sample succeeds, rename a small batch and verify the first, middle, and last files against the old-to-new map. Stop if a document opens in the wrong application, a file is missing, or two names refer to the same destination. The slug generator cannot validate those outcomes; the inspected copy and destination test are the release gate for the naming change.

Common questions

Does the Slug Generator guarantee a Windows-safe filename?

No. It cleans punctuation and applies text-formatting choices, but it does not check reserved device names, duplicates, the extension, the complete path, or destination-specific restrictions. Treat its output as a candidate base.

Can I keep spaces and uppercase letters in a Windows filename?

Yes, ordinary spaces and uppercase letters are not on Microsoft’s reserved-character list. A dash-and-lowercase style can improve consistency, but it is a project policy choice. Do not use capitalization alone to distinguish files.

Why must I display the extension before renaming?

The extension identifies the file type and helps Windows choose an application. Keeping it visible lets you change only the base and verify that .docx, .xlsx, .pdf, or another real ending remains unchanged.

Will changing .docx to .pdf convert the document?

No. Microsoft Support states that changing an extension changes only the filename. Use the source application’s export feature or a real format-conversion workflow when the required file format changes.

What should I do if the name works locally but fails on a shared drive?

Keep the original and test copy intact, record the exact error, and check the shared drive or service rules. Shorten or revise the candidate only after identifying the destination restriction, then repeat the destination test.

Can ToolboxHub rename a folder of Windows files for me?

No. The Slug Generator and Online Notepad process text in the browser. File copying, extension checks, renaming, backups, collision handling, and content verification remain in your approved Windows file workflow.