What does the safe filename and path checker produce?
Check single filenames and explicitly declared relative paths for traversal, reserved names, incompatible characters, normalization collisions and file/directory conflicts.
The working area above runs the supported validator in the browser. It keeps the result inspectable and preserves every unresolved item for responsible review.
What do you need before you start?
- Prepare one comma-separated UTF-8 CSV, one-sheet text-cell XLSX starting at A1, or rectangular dataset JSON.
- Keep the unchanged original source and confirm the intended destination application.
- Review unresolved interpretations before using any date, export cell or package name.
What information do you enter?
Prepare only the bounded inputs listed below for this validator.
- Exactly one Path, File path, Filename or File name heading.
- Optional Kind or Path kind, declaring Single filename or Relative path.
- Optional Record ID, Record reference or Reference heading.
What you can download
Every result must identify its supplied facts, assumptions and unresolved items.
| Free result | Included downloads |
|---|---|
Enter your information, inspect the on-screen result and keep a browser backup. Editing and direct copies of your entered information stay free. |
These supported outputs are free. No checkout is required. |
Fictional review report (PDF). Editable sample (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the free finalized pack renderer.
How does the safe filename and path checker work?
- 1Select a local source
Choose one supported file or load the clearly fictional example. Source files remain unchanged.
- 2Inspect supported checks
Check single filenames and explicitly declared relative paths for traversal, reserved names, incompatible characters, normalization collisions and file/directory conflicts.
- 3Review unresolved items
Inspect escaped previews, source-row pointers and complete result downloads. Confirm the intended interpretation separately.
- 4Download the free review pack
Download PDF, DOCX, Excel, CSV, complete parsed source JSON, delivered-file hashes and instructions. Keep the original source separately.
Method and sources
Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.
- Naming Files, Paths, and NamespacesWindows reserved device names, characters and path constraints. This portable profile uses conservative bounds and does not guarantee every destination. Supported review method.Microsoft. Reviewed 2026-10-06.
- Path TraversalTraversal and path interpretation risks. The tool reviews declared package names without decoding, writing or extracting files. Supported review method.OWASP Foundation. Reviewed 2026-10-06.
Common questions
What information does the safe filename and path checker need?
Enter exactly one Path, File path, Filename or File name heading; optional Kind or Path kind, declaring Single filename or Relative path; optional Record ID, Record reference or Reference heading. Prepare one comma-separated UTF-8 CSV, one-sheet text-cell XLSX starting at A1, or rectangular dataset JSON.
What does the safe filename and path checker produce?
Formal PDF and editable DOCX review reports Excel checks and escaped source previews Complete findings CSV Complete parsed source and result JSON Delivered-file SHA-256 manifest and review instructions Unchanged original source download Review unresolved findings and limitations before use.
Who makes the final decision?
A responsible person reviews the result. The portable package profile is deliberately conservative. It checks names without creating or extracting files. It does not resolve symbolic links, verify an extraction destination or establish that file contents are safe. Destination systems may impose additional limits.
Is this tool free?
Yes. The on-screen result and listed downloads are free. No checkout is required. Keep local backups and review the stated method and limits.
Can I use the safe filename and path checker for this task?
Flag unsafe filenames and declared relative paths, including traversal, reserved names and naming conflicts. The portable package profile is deliberately conservative. It checks names without creating or extracting files. It does not resolve symbolic links, verify an extraction destination or establish that file contents are safe. Destination systems may impose additional limits.
What still needs review?
The portable package profile is deliberately conservative. It checks names without creating or extracting files. It does not resolve symbolic links, verify an extraction destination or establish that file contents are safe. Destination systems may impose additional limits.
Previews are abridged after 400 characters. PDF and DOCX show the first 100 assessments. Complete results and parsed values remain in Excel, CSV and JSON.
Original files stay in this browser. Download original source preserves its bytes. Restore it through Select file.