How to clean filenames for uploads and archives

Choose a portable filename baseline

A conservative portable name uses letters, digits and a consistent separator such as a hyphen or underscore. This avoids many problems caused by slashes, control characters, trailing spaces and punctuation that operating systems, archive tools, content management systems and URLs interpret differently. Lowercase names also reduce confusion on systems where Report.pdf and report.pdf may be treated as either different files or the same file.

Portability does not require stripping every meaningful character from every language. Unicode filenames work in modern systems, but normalisation, keyboard input and third-party integrations can still vary. Decide whether readable local-language names or a restricted ASCII convention best fits the actual recipients. Apply the same documented choice across a batch instead of transliterating some names and not others.

• Use one separator consistently and collapse repeated separators.
• Remove leading and trailing separators, dots and spaces.
• Avoid path separators and invisible control characters.
• Keep names descriptive enough to identify without opening the file.

Preserve extensions deliberately

The final extension often tells an application how to handle a file. A cleanup workflow should separate it from the base name, clean the base, normalise extension case if desired and then reattach it. Renaming holiday-photo.JPG to holiday-photo.jpg is usually harmless, while dropping .jpg or changing it to .png does not convert the image's encoded format.

Compound extensions need a decision. For an archive such as project-backup.tar.gz, preserving only the final .gz extension keeps a valid file but hides that it contains a tar archive. A batch intended for developer assets may preserve recognised compounds, while a general upload workflow may treat the final suffix as the extension. Check unusual names manually rather than assuming every dot separates a disposable label.

Build names from stable, useful information

A name works best when it describes the asset rather than its temporary editing state. Subject, purpose, variant and a meaningful date can be useful components. Words such as final, newest and copy become unreliable as soon as another revision appears. If versions matter, use an agreed sequence such as v02 or a revision date in unambiguous YYYY-MM-DD form.

Prefixes and suffixes should earn their space. A project code can group related exports, a language code can distinguish translations and dimensions can identify image variants. Do not put passwords, personal identifiers, confidential case details or access tokens in filenames: names often appear in browser history, download lists, server logs, archive indexes and shared links even when file contents are protected.

Check batch cleanup for collisions

Different originals can collapse to the same suggestion. Report 1.pdf and report-1.pdf may both become report-1.pdf after spaces and punctuation are normalised. Case folding creates another collision when Logo.PNG and logo.png share a destination. A safe batch workflow compares the complete proposed set before any rename or upload begins.

Resolve collisions predictably with a stable suffix, sequence or genuinely unique identifier. Numbering should be calculated across the complete batch so repeated previews do not produce shifting names. Exporting a before-and-after mapping creates a review and rollback record, but the mapping itself must quote commas, line breaks and spreadsheet-sensitive values correctly when stored as CSV.

• Compare suggestions case-insensitively when the destination may ignore case.
• Include the extension when checking for a full-name collision.
• Review blank results created from names containing only removed characters.
• Keep the source-to-suggestion mapping until the upload or rename is verified.

Treat archive names and uploads as untrusted input

Cleaning a visible filename improves compatibility; it does not make a file safe. A server must still generate or validate its own storage path, reject path traversal, enforce size and type limits, inspect content where appropriate and prevent overwriting. Never concatenate an uploaded name directly into a filesystem path merely because a browser tool removed suspicious punctuation.

Archives add another layer because entries can contain nested paths, links and names that behave differently when extracted. Renaming the outer ZIP file does not clean anything inside it. Extract untrusted archives only with software that prevents entries from escaping the chosen directory, and review the internal hierarchy before publishing or sharing the result.

• Do not infer file type or safety from the extension alone.
• Do not expose private names through public asset URLs.
• Keep server-side upload controls independent of client-side cleanup.
• Scan archive contents and apply the destination's security policy before extraction.

Avoid common cleanup mistakes and know the limits

Common mistakes include renaming an extension as if it converted the file, applying changes before checking collisions, removing identifiers needed by recipients and using a title that exceeds the destination's full path limit. Keep suggestions reasonably concise, but remember that limits can apply to a whole path rather than one filename. Reserved device names and trailing-character rules also differ between operating systems.

A browser filename cleaner can read names from selected File objects and propose replacements without opening their contents, but ordinary web pages cannot rename arbitrary files on a device. You must apply the suggestions through the operating system, upload workflow or an authorised batch-renaming application. Some platforms will rename uploads again, so verify the final stored and public names rather than assuming the suggestion is the last transformation.

• Test a small representative batch before applying a large rename.
• Keep backups when names are referenced by code, documents or external systems.
• Confirm that links and manifests are updated after a real rename.
• Use the destination's published naming rules when they are stricter than the general convention.

Put this guide into practice

These free PipFoxy tools are directly related to the method above. No account is required, and current tool content stays in your browser.

Or browse the full creator tools category.