Inspect a Local Audio or Video File
Choose the right starting point
Open Inspect a file on the homepage and choose one audio or video file. The file does not need to come from this site. A recording you made yourself, an authorized export or a test clip will work if your browser supports its media format. The tool creates a temporary browser URL for that file; it does not turn the file into a publicly accessible link or upload its contents. Clearing the tool or leaving the page releases that temporary URL.
Read the measurements, not a quality score
File size is the number of bytes in the selected file. MiB means 1,048,576 bytes, so it differs from a storage label using decimal megabytes. Duration and video dimensions come from the browser media decoder. A 1920 x 1080 result describes frame dimensions, not sharpness, original camera resolution or a promise of good picture quality. Audio-only files have no video dimensions. The inspector does not claim to identify every codec, audio sample rate or channel configuration.
Understand the bitrate estimate
The tool divides the total file size in bits by playback duration. For example, a 12,000,000-byte file lasting 60 seconds has an estimated total rate of 1.6 Mb/s. That includes container overhead and all streams in the file. It is not a measurement of the video stream alone and cannot reveal how a variable-bitrate encoder distributed bits across scenes. If duration is missing or infinite, the estimate remains unavailable instead of using a guessed duration.
Use SHA-256 to compare copies
For files up to 64 MiB, Calculate SHA-256 reads the file on your device and calculates a checksum with the browser's Web Crypto API. Compare the result with a checksum calculated from another copy: a match is strong evidence that the bytes are identical. A checksum does not prove that the file is safe, licensed, authentic or free of malware. This limit keeps the in-memory calculation manageable on phones. For larger files, use a trusted local checksum utility.
Save a report and handle failures
Save report creates a plain-text summary in a supported browser. The report control is disabled in Android WebViews whose native handler cannot save browser-generated files; file properties can still be read on screen. A report saved before metadata finishes may contain Unavailable values; wait for File inspected before saving the final copy. If the browser cannot play the file, size and the reported file type can still be inspected. Try a compatible local player to distinguish an unsupported codec from a damaged file. Renaming a file extension does not convert its media. No inspector result grants permission to distribute somebody else's recording.