Guides / BlankLogo

Inspect a video's metadata before starting a cleanup edit

A practical pre-edit workflow for checking video metadata before cleanup, with an ffprobe example, a comparison table, and review steps.

November 5, 2026 · 10 min read · BlankLogo

A cleanup edit can go wrong before you touch the picture. Imagine you have a short clip you’re allowed to edit, the unwanted mark sits in one corner, and the file seems normal because it plays without errors. Then the cleaned export comes back slightly reframed, softer than expected, or just different enough to break continuity with nearby shots. The visible problem was the mark. The hidden problem was skipping a baseline check.

That baseline is metadata. Before you crop, mask, or upload anything, inspect the source so you know what you started with. This is especially relevant when the cleanup path itself may change framing or involve re-encoding. BlankLogo says cropping can change the frame, processed video may be re-encoded, and the export should be reviewed before download (BlankLogo). So the practical goal is not only to clean the clip, but also to verify what changed.

Why metadata matters before cleanup

For this proposed review, start by recording four items:

• duration
• resolution
• codec
• frame rate

These are not the only properties a file can have, but they are a strong starting baseline for pre-edit review.

That matters because video is normally compressed; uncompressed video requires very large storage and bandwidth, and MDN notes that most video codecs are lossy rather than exact reproductions of the source (MDN). It also matters because a media file can contain multiple streams, not just one video track; FFmpeg’s documentation describes inputs and outputs as containing elementary streams such as video, audio, subtitle, attachment, and data streams (FFmpeg).

In plain terms: a filename and extension do not tell you enough. Two .mp4 files can differ in codec, frame rate, dimensions, duration, and stream makeup. If you only judge by playback, you may not notice a mismatch until after the cleanup export.

A practical ffprobe starting point

If you want a command-line baseline, ffprobe is the FFmpeg inspection tool documented separately from ffmpeg itself (ffprobe). A practical starting command for the first video stream is:

ffprobe -v error \
  -select_streams v:0 \
  -show_entries stream=codec_name,width,height,r_frame_rate,avg_frame_rate,duration:format=duration \
  -of default=noprint_wrappers=1 "input.mp4"

Use that as a pre-edit snapshot, then run the same command on the cleaned export so you can compare like with like.

A few cautions help here:

• This command targets v:0, the first video stream.
• Different files may report some values at the stream level, format level, or both.
• You are using the output as a baseline for comparison, not as a guarantee of quality.

Hypothetical example with synthetic output

codec_name=h264
width=1920
height=1080
r_frame_rate=30000/1001
avg_frame_rate=30000/1001
duration=15.015000

How to read that baseline:

• codec_name identifies the encoded video stream.
• width and height give the stored frame dimensions.
• r_frame_rate and avg_frame_rate show frame-rate values to compare before and after.
• duration gives clip runtime for a quick identity check.

The most important habit is consistency: inspect the source, save the result, then inspect the export with the same command.

How to interpret the four fields

Duration: confirm you have the right clip

Start by comparing the expected and reported duration.

If you expected about 15 seconds and your source reports about 8 seconds, stop and confirm the asset before doing any cleanup work. Even when the value is not perfectly round, it still helps you verify clip identity and later compare whether the export preserved timing.

What to do:

• Note the expected runtime before you inspect.
• Compare that expectation to the reported duration.
• After cleanup, confirm the export duration still matches your intent.

How to check the result:

• If the export is shorter or longer than expected, review whether trimming or processing altered it.
• If the duration matches but playback still feels wrong, check frame rate next.

Resolution: estimate the cost of a crop

Resolution tells you how much room you have to remove picture area.

A corner cleanup that trims a few pixels from a large frame may be acceptable. The same crop on a smaller frame may be much more noticeable. This matters because BlankLogo explicitly says cropping can change the frame (BlankLogo).

What to do:

• Record the original dimensions before cleanup.
• Estimate how much image area the unwanted mark occupies.
• Decide whether a crop-based fix will materially affect composition.

How to check the result:

• Compare source and export dimensions.
• Watch the export at normal size and full size.
• Look specifically at headroom, lower-third text, and edge composition.

Codec: understand the compression context

Codec tells you what kind of encoded video stream you are dealing with. MDN lists common web video codecs including AV1, AVC/H.264, HEVC/H.265, VP8, and VP9, and notes that containers such as MP4 or WebM may support different codec combinations (MDN).

That leads to two practical rules:

• container is not the same thing as codec
• re-encoding may change picture characteristics even when the file still plays normally

Because most common video codecs are lossy, a cleanup export that is re-encoded should be reviewed rather than assumed equivalent to the source (MDN).

How to check the result:

• Compare the reported codec on source and export.
• If the codec changed, review playback compatibility and picture quality.
• Even if the codec did not change, still check detail retention visually.

Frame rate: protect motion and sync expectations

Frame rate affects how motion is represented and compared. A clip reported as 30000/1001 is about 29.97 fps; 24000/1001 is about 23.976 fps.

What to do:

• Record the exact reported value, not just a rounded description.
• Compare source and export values directly.
• If you are matching other shots, keep the original value in your notes.

How to check the result:

• If source and export differ, review motion and timing carefully.
• If the cleaned clip feels subtly different but duration matches, frame-rate mismatch is one of the first things to rule out.

Fully worked example: baseline, cleanup decision, and verification

Hypothetical example using synthetic data

Suppose you own or have permission to edit a file named launch-demo.mp4. An unwanted mark sits in the lower-right corner.

First, inspect the source:

ffprobe -v error \
  -select_streams v:0 \
  -show_entries stream=codec_name,width,height,r_frame_rate,avg_frame_rate,duration:format=duration \
  -of default=noprint_wrappers=1 "launch-demo.mp4"

Synthetic source output

codec_name=h264
width=1920
height=1080
r_frame_rate=30000/1001
avg_frame_rate=30000/1001
duration=15.015000

Now turn that into a decision.

• Confirm clip identity

You expected a clip of about 15 seconds. The reported duration is consistent with that expectation.

• Record the baseline

Save these values in a note:

• duration: 15.015 s
• resolution: 1920×1080
• codec: h264
• frame rate: 30000/1001

• Estimate crop impact

Assume the unwanted area can be removed by trimming about 120 pixels from the right edge and 80 pixels from the bottom edge. That would change the stored frame from 1920×1080 to 1800×1000. On a large frame, that may be acceptable, but it will still change composition.

• Process one review export

If you use a tool whose cleanup path may crop or re-encode, do not treat the first export as final. BlankLogo specifically advises reviewing the processed export before downloading, and notes that cropping can change the frame and processing may involve re-encoding (BlankLogo).

• Inspect the export with the same command

Synthetic export output

codec_name=h264
width=1800
height=1000
r_frame_rate=30000/1001
avg_frame_rate=30000/1001
duration=15.015000

• Compare source and export

• Do the visual check

Metadata alone is not enough. Play the export and look for:

• framing changes at the right and bottom edges
• softened detail after processing
• any timing or motion oddities despite matching duration

This is the key idea: metadata tells you what changed structurally, and playback tells you whether the change is acceptable.

A reusable checklist you can keep next to the edit

Use this before and after every cleanup pass on media you own or are allowed to edit.

If you prefer a decision procedure instead of a table, use this:

• Confirm you have permission to edit the clip.
• Inspect the source and save the output.
• Write down duration, resolution, codec, and frame rate.
• Estimate whether cleanup is likely to change framing.
• Process a review export, not a presumed final export.
• Inspect the export with the same command.
• Compare the four key fields.
• Review the export visually before accepting it.

Assumptions, limits, and common mistakes

Assumptions

This workflow assumes:

• you are working only on media you own or have permission to edit
• your goal is careful preparation, not guaranteed restoration
• you can inspect source and export files before accepting the result

It also assumes you understand the difference between technical properties and visual quality. FFmpeg describes media handling as a pipeline involving demuxing, decoding, filtering, encoding, and muxing (FFmpeg). That is a useful reminder that matching metadata does not automatically mean matching image quality.

Limits

Metadata inspection cannot tell you everything. It will not prove:

• whether fine texture was softened
• whether a fill or inpaint looks natural across frames
• whether a crop damaged composition in a way that matters to the shot

That is why BlankLogo’s review step matters: if the frame may change and the video may be re-encoded, the export should be checked before you keep it (BlankLogo).

Common mistakes

Confusing container with codec An .mp4 extension does not tell you the whole encoding story. MDN’s codec guide makes clear that containers and codecs are separate concepts with specific compatibility combinations (MDN).

Rounding frame rate too casually For casual discussion, 29.97 and 30 may sound close. For comparison work, record the exact value.

Skipping the post-export inspection If you inspect only the source, you still do not know what cleanup changed.

Treating playback as the only test A file can play normally and still differ in duration, dimensions, or frame rate.

Ignoring the possibility of reframing If the cleanup method uses cropping, compare dimensions and then judge whether the new composition is acceptable.

What to do before your next cleanup edit

Before the next cleanup job, run one metadata pass before processing and one after. Save both results. Then compare duration, resolution, codec, and frame rate before you decide the export is acceptable.

That habit will not guarantee a perfect restoration result, and it does not replace visual review. What it does give you is a factual baseline: what the source was, what the export became, and whether the change matches your intent. For cleanup work on media you own or may edit, keep that baseline with your review notes.