File Metadata Reader
Drop or pick a local file to read metadata — name, size, type, last modified and more; read entirely on-device, nothing is uploaded.
>_ USAGE GUIDE
Drop a local file onto the page or pick it with a file selector, and its metadata is shown right away: name, size, type (MIME), and last-modified time, all in one glance. It is read entirely on-device — the file is never uploaded to any server.
File metadata is the "data about the file": beyond the content itself, the OS and browser record its name, byte count, format, and modification time. When you need to confirm a file's real size, find out its MIME type, or check when it was last modified, dragging it in here is faster than digging through system properties.
- Drop the file: drag it onto the page to see its name, size, type, and modification time immediately
- Check the format: confirm the MIME type, handy for spotting a mismatch between extension and actual format
- Read the size: see the volume in bytes/KB/MB to judge whether a file is oversized
Everything runs locally in your browser — file contents are never read or uploaded, so it is safe to drag in sensitive files just to inspect their properties.
>_ FAQ
Q1 · What fields does file metadata include?
Common ones: name, size (byte count, usually shown converted to KB/MB), type (MIME such as image/png), and last-modified time, plus whatever else the browser/OS exposes (on the Web, the File object gives name, size, type, and lastModified). Different sources expose slightly different fields, but these core properties are usually all present.
Q2 · Does reading file info upload my file?
No. This tool reads the metadata of the file you drop using the browser's local APIs — the file content never leaves your device and nothing is sent to any server. Only property-level information is shown, fully offline, so sensitive files are safe to inspect.
Q3 · Why is the type sometimes empty or wrong?
The browser usually derives a file's type from its extension or system inference, which is not fully reliable: unknown file types may come back empty or as application/octet-stream, and extensions can be renamed without the inference keeping up. The most reliable way to know the true format is to read the magic bytes (the signature at the start of the file). Treat the displayed type as a reference and combine it with the extension and content if it looks off.
Q4 · What units is file size shown in, and how do bytes and KB relate?
The display usually pairs raw bytes with a human-readable conversion: 1 KB = 1024 bytes, 1 MB = 1024 KB, 1 GB = 1024 MB. KB/MB are more intuitive for a single file's size; the exact byte count matters more for judging storage cost or whether it exceeds an upload limit.
Q5 · When is reading file metadata useful?
Figuring out "why is this file so big", confirming the true type and modification time of a received or downloaded file, spotting an extension/content mismatch, checking a file against an upload size limit beforehand, and inspecting properties before scripting automated handling — for all of these you can drag the file in and read its metadata without installing anything.