Sensitive File Detector
Scan a batch of files — by name, extension, and readable content — to flag credentials, keys, and config files before you upload, share, or commit them.
How to use Sensitive File Detector
- Add the files you want to review, such as a project batch before committing or sharing it.
- Select Scan Files. Review each file’s risk level and the reason it was flagged; text content is checked only for supported text extensions under 2 MB.
- Choose Export Report (CSV) to save the findings. Treat risk levels as indicators, not proof: binary file contents and unrecognized secret formats are not scanned.
What this checks for
Before zipping up a project to share, or dragging a folder into a public repository, it's worth a quick pass for files that were never meant to leave your machine — environment files, private keys, database dumps, or config files with embedded credentials. This tool flags them by filename pattern and, for readable text files, by scanning content for common secret-shaped strings.
Scan a project before committing or sending files
Add a batch of files to check risky names such as .env, private-key extensions, and credential files. For supported text-like extensions, the scanner also checks readable files smaller than 2 MB for common password assignments, API-key patterns, private-key headers, database connection strings, and AWS access keys. Results are grouped by a heuristic risk level and can be exported as a CSV report.
Use the findings as a review checklist before creating a public repository commit, attaching a project archive, or handing files to another team. This is a pattern-based local scanner, not a full secret-detection engine: binary contents are not inspected, larger text files are skipped, and unfamiliar credential formats may not match its rules.
Does it open binary files?
No — content scanning only applies to files that can be safely read as text (code, config, JSON, env files, etc). Binary files like images or archives are only checked by filename.
Why can a file be flagged even when it contains no secret?
Filename and content patterns are indicators, not proof. Review the reason shown for each result and decide whether the file actually contains sensitive material.
Does a low-risk result guarantee a file is safe to share?
No. The scanner only checks supported names and text patterns within its size and file-type limits. Manually inspect important files and use your normal secret-scanning checks before publishing.