Video Metadata Inspector in the browser is not a generate
/free-tools/video-metadata-inspector never spends a credit. Do not pay a model to do an in-browser file job.
/free-tools/video-metadata-inspector never spends a credit. Do not pay a model to do an in-browser file job. Drop a clip, read what the file actually contains — dimensions, duration, aspect ratio — on your machine. Nothing is uploaded. It is not a line on what it costs.
Versely has no free generation tier. Every generate costs credits. The inspector is free because it never calls a model. Prompting a video row to "check if this is 1080×1920" is how a file-info question becomes a bill.
The video element is the source of truth
The tool creates an object URL, loads it into a <video>, and reads videoWidth, videoHeight, and duration when metadata fires. It also shows filename, byte size, MIME type, a reduced ratio (1080×1920 prints as 9:16), and orientation.
That is the real file, not the name. Chat apps and cloud drives silently transcode. A 1080×1920 export can arrive as 720×1280. Platforms reject on real dimensions and duration. Check the file before a platform does.
Nothing is sent to a server. Disconnect the network; the numbers still appear. Same architecture as the rest of free tools: work on the device, no account, no watermark.
Frame rate is not this page
Browsers expose dimensions and duration. They do not expose a trustworthy fps figure. Sampling is wrong often enough to be worse than none, so the inspector does not guess. When fps is load-bearing, use ffprobe. Do not ask a model to "read the frame rate." You will get a new clip.
The inspector also does not report colour boxes, codec profiles, or loudness. Geometry and duration only.
If you needed a still from the same file, the sibling is the video frame extractor: scrub, export a PNG at native pixel size, still zero credits. The inspector tells you the box. The extractor gives you the frame. Neither invents pixels.
Credits start when you invent a second file
/cost groups structurally different credit formulas: per second, per thousand characters, per megapixel, per job. Reading width is not one of them. A generate that "also happens to come out 9:16" is a generate. You paid for motion. You did not need to pay to learn the ratio.
The expensive mistake is regenerating because the filename said 1080p and the upload bounced. Open the file here first. If the dimensions are already wrong, recode locally — or generate only if you need new picture, not a new box.
"Make this the same length as the last take" is a duration read plus a trim, not a second render. Duration is on this page.
The file-vs-prompt test
Already have the clip, only need to know what it is → inspector.
Do not have the clip → that is a generate, quoted in credits before you confirm.
Have the clip and need different picture → that is a generate. The inspector still tells you what you started with.
Fifty-three free tools on this surface never touch a model. Credits are for the ones that invent.
FAQ
Does the video metadata inspector spend credits if I am logged in?
No. It never spends a credit. There is no account on the tool, and logging into Versely elsewhere does not meter a local video element. Generation is the surface that shows a cost before you confirm.
Why doesn't it show frame rate?
Browsers do not expose a trustworthy fps value through the video element. Guessing by sampling is often wrong. The tool refuses to invent a number. Use ffprobe when frame rate matters.
Why does the size differ from what I exported?
Usually because something in the chain re-encoded it. Messaging apps and cloud drives transcode without asking. Checking the real file is how you catch a 720×1280 stand-in before a platform rejects a "1080p" upload.
Why is this free if Versely has no free generation tier?
Because it is not generation. Free tools run on your device; they cost nothing to run. /cost is the catalogue of jobs that do cost credits. Do not mix the two to "inspect" a file.