Step 1 / source
Choose the source
Drop one file here
Choose the file whose extension or reported type you need to sanity-check.
Checking publication status...LOCAL FILE INSPECTOR / TYPE SIGNALS
Compare a file extension, the browser-provided MIME claim, and known leading-byte signatures in one downloadable report.
Step 1 / source
Choose the file whose extension or reported type you need to sanity-check.
Checking publication status...This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.
The converter creates a separately named output. It never writes back into the source file.
One file up to 2 GB. Only the first 8 KB is read; the signature catalogue is intentionally finite.
Plain-language method
Extensions are user-editable, browser MIME values can be empty, and signatures cover only known formats. The report shows all available signals instead of pretending any single one is absolute proof.
Choose the exact file you plan to upload, serve, or convert. Large files are safe to inspect because only a small header slice is read.
There are no guesses to tune. Known signatures take priority, then extension mapping, then unknown.
Review the on-page JSON and optionally download the _nirmion_tools_mime_report.json file.
Useful when
Before converting
Know the boundary
The checker does not parse the complete format, verify embedded objects, or establish safety. A spoofed or polyglot file can need deeper analysis.
Quick answers
MIME inspection is useful when its confidence is understood.
Browsers often infer type from the extension and may provide no claim for uncommon formats.
Known signature bytes and the filename extension point to different format families.
No. It identifies a bounded set of file signatures and performs no malware detection.