Processed in your browser

Media inspector

Inspect file type, dimensions, duration and file size; optionally calculate its hash.

No account required
Choose a file stored on your device. Local tools do not upload it to Vaultxon.

Why inspect a file first?

An inspector helps answer basic questions before a conversion: how large is the file, what type does the browser report, does it expose image dimensions or media duration, and is the file likely to be the one you intended to select? This is useful when a file has a misleading extension or came from several export tools.

The browser’s reported MIME type can be empty or generic, especially for local files. Dimensions and duration depend on whether the browser can decode the media. A file extension alone is not proof of its actual container or codec.

Read the results carefully

File size is normally shown in bytes and may be formatted into KB or MB for readability. Image dimensions are pixel width × height. Media duration is measured in seconds and can differ slightly from a rounded display. These fields are clues, not a forensic media analysis report.

If the inspector also calculates a hash, use it to compare byte-level integrity with a trusted checksum. Do not confuse the checksum with the media codec or a malware verdict. If the file is important, verify its source and scan it using your normal security workflow.

Choose the next tool

For an oversized image, use Resize & Convert Images or WebP conversion and compare visual quality. For a video that is too large, try the compression tool on a short sample. To extract audio, use Video to audio and verify the exported track. If subtitles appear out of sync, inspect the subtitle file structure and use a subtitle editor rather than guessing from the filename.

Run one operation at a time and keep the original. This makes it easier to identify which setting caused an output difference.

Privacy and troubleshooting

The selected file is inspected inside the browser in this build. If the file type, dimensions or duration are missing, the browser may not recognize the format or may be unable to decode it. Try a standard export from the original application or a shorter sample.

Do not upload confidential material to a public sharing service merely to inspect it. Also remember that local processing does not prevent the browser from making ordinary network requests to load the page and libraries.

Frequently asked questions

Does the inspector reveal every codec?

No. Browser metadata and decoding support vary. Use a dedicated media information utility for detailed stream-level analysis.

Does a file extension prove the format?

No. Extensions can be renamed or incorrect. MIME type and successful decoding provide additional clues but are not a complete forensic test.

Is the SHA-256 result a safety scan?

No. It is a digest used for comparison, not a malware detector.

Technical references

Treat metadata as a clue, not a verdict

Use the reported type, dimensions and duration to decide the next troubleshooting step, then verify by opening the file. For detailed codec profiles, stream layout or archival inspection, use a dedicated media-analysis application.