ContextCleaner: see every entry in the Windows 11 right-click menu, and which app added it — on the Microsoft Store.

Last updated:

Guided workflow variation

FFmpeg extracted frame JPEG metadata differs from parent video?Here's exactly why — and how to control it.

When you pull stills from a clip, FFmpeg writes its own encoder tags and drops the camera, timeline, and location data the video carried. MetaForge lets you normalize every extracted frame — strip the artifacts or stamp intentional metadata — in one local batch on Windows, previewed before anything is written.

Extracted frames rarely match their source video's metadata. MetaForge normalizes a whole folder of frames locally — strip encoder tags or stamp consistent fields — previewed before any write.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Get it from Microsoft

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Full MetaForge overview
One-time purchase No telemetry Local-first

local-first · buy direct · one-time purchase · no telemetry

If this sounds like your week

The still you exported is not the file the camera made.

Pull a frame out of a clip and the JPEG that lands in your folder tells a different metadata story than the source video. FFmpeg stamps each still with its own software and encoder strings, a generic or empty timestamp, and none of the camera, capture-time, or GPS fields the original recording held. People search for this the moment an archivist, editor, or reviewer notices the mismatch and asks which file to trust.

Where tooling usually breaks

Re-running ExifTool flags per frame doesn't scale to a whole clip.

You can memorize a string of ExifTool flags and run them frame by frame, but a single clip can yield thousands of stills, and one missed field or wrong tag ships the inconsistency you were trying to remove. Uploading frames to an online metadata stripper adds a third party to material that is often sensitive — exactly the wrong move for newsroom, legal, or investigative work.

Parent video vs. extracted frame

Parent video vs. extracted frame 
> ffmpeg -i clip.mp4 -frames:v 1 frame.jpg

# Parent video — clip.mp4
#   Make/Model:  Sony ILCE-7M4
#   CreateDate:  2026:03:14 09:21:05
#   GPS:         43.6532, -79.3832

# Extracted still — frame.jpg
#   Software:    Lavf60.16.100
#   CreateDate:  (none)
#   Make/Model:  (none)
#   GPS:         (none)

Where MetaForge lands

Normalize every extracted frame in one local pass.

MetaForge points at the folder of stills FFmpeg produced and gives you deterministic control over their metadata: strip the encoder and software tags so the frames carry nothing misleading, or stamp a consistent, intentional set of fields — caption, copyright, author, date — across the entire batch. Everything runs on your Windows machine with a Simulation Report that previews every change before a single file is written, so exhibits and published stills show the metadata you chose, not encoder artifacts.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Get it from Microsoft

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Learn more about MetaForge

local-first · buy direct · one-time purchase · no telemetry

What you get

Feature highlights

Privacy Mode

Strip GPS coordinates, altitude, and camera serial numbers from a whole folder locally — no browser uploader, no cloud service.

Simulate Run preview

Generate a Simulation Report of every planned move and rename, flagged name collisions, and RAW count before a single file is touched.

EXIF-aware Auto-Organize

Build folder structures from Year, Month, Camera Make, Camera Model, and file extension — route in place, into a sibling folder, or to a specific destination.

Batch rights & IPTC

Write copyright, author, and keyword fields across thousands of files at once, with XMP sidecar sync (Skip, Merge, or Backup & Merge) for RAW photos.

Rust-powered throughput

Saturate local CPU cores for fast scans and metadata operations on tens of thousands of files, with keep-originals copy mode and a live progress overlay.

Local-first and global

100% offline, no telemetry, no account, with a fully translated interface in 20 languages. One-time purchase on the Microsoft Store. One-time purchase. No subscriptions. Local-first.

Especially when

  • Strip GPS and sensitive photo metadata before sharing images with clients or platforms
  • Preview exactly what a batch metadata job will do before any file is changed
  • Organize large photo libraries locally by EXIF date, camera model, or lens
  • Batch-write copyright and IPTC keywords without sending files to cloud tools

Who benefits

Real-world scenarios

Newsroom producer publishing video stills

You pull frames from source footage to illustrate a story. The exported JPEGs carry an FFmpeg software tag and a blank capture date, while the original clip had the real timestamp and camera model. A fact-checker flags the mismatch before publication.

You run the frame folder through MetaForge, strip the encoder tags, and stamp one consistent caption and date across every still. Simulate Run confirms the changes first, so the published images show intentional metadata instead of encoder noise.

Investigator preparing exhibit stills

Extracted frames need to go into an exhibit set, but each one carries FFmpeg's encoder strings and no usable timestamp, which invites questions about how the file was produced and whether it can be trusted.

MetaForge normalizes the whole batch locally — either clearing metadata entirely or applying one documented field set — so the exhibit frames are consistent and nothing leaves the workstation.

Archivist standardizing a frame library

A research archive holds thousands of stills extracted from many videos over the years, each with different, encoder-derived metadata that makes the collection impossible to compare or search reliably.

MetaForge applies one metadata rule across the entire folder in a single pass, with a preview of every change, turning an inconsistent dump into a uniform, catalog-ready set.

Deep dive

Why extracted frames and their source video never share metadata

A video file stores its metadata at the container level. In an MP4 or MOV, fields like creation time, camera make and model, and GPS live in the container atoms, separate from the encoded picture data. The individual frames inside the stream are just compressed pixels; they have no embedded EXIF of their own.

When FFmpeg writes a frame out to JPEG, it creates a brand-new image file through its still-image encoder. That file is stamped with FFmpeg’s own identifiers — commonly a Software tag such as "Lavf" or "Lavc" with a version number — and a generic or empty timestamp. The container-level camera, capture-time, and location fields do not propagate, because the still-image output path does not map them into EXIF. So the difference you are seeing is structural, not a bug: the parent video’s metadata stays in the container, and each extracted JPEG starts from the encoder’s defaults.

That gap matters most when provenance matters. An archivist comparing a still to its source, a fact-checker validating a timestamp, or counsel reviewing an exhibit will find a divergent date and an unfamiliar software string and have to explain it. MetaForge closes the gap by operating on the extracted frames after FFmpeg: point it at the folder and either strip the encoder and software fields so the stills carry nothing misleading, or write one consistent, intentional set of fields — caption, copyright, author, date — across every frame. It does not reach back into the MP4 to copy the camera’s original tags; it gives you control over exactly what the frames declare, which is what consistency and chain-of-custody clarity actually require. A Simulation Report previews every change before anything is written, originals can be preserved by copying, and the whole pass runs locally on a Rust engine with no uploads.

exiftool frame.jpg
Software     : Lavf60.16.100
Create Date  : (none)
GPS Position : (none)
# parent clip.mp4: Sony ILCE-7M4, 2026-03-14, GPS present
After MetaForge batch normalize
Software     : (removed)
Create Date  : 2026:03:14 09:21:05
Copyright    : (c) 2026 Newsroom
Comment      : Still extracted from clip.mp4
Trusted by pragmatic desktop users

Built for people who prefer tools that stay local.

Real workflows: focus timers that stay visible, batches that never leave the disk, and renames you can rewind.

Customer review 01

PinPoint: Always On Top saves me so much time as I can organize all my report materials without having to flip between windows or tabs. I love the fact that it is straightforward and simple.

Senior Accountant · Manufacturing Company · United States · PinPoint Reviewed About PinPoint
Customer review 02

I used to get so frustrated when my Taskbar would freeze and disappear. Taskbar Sentinel has eliminated that pain without subjecting me to another subscription.

Darren · Calgary, Alberta, Canada · Taskbar Sentinel Reviewed About Taskbar Sentinel
Customer review 03

OpticBatch and MetaForge are a lifesaver for me as a person with a passion for photography. They give me the ability to stay organized and keep personal information confidential when I post pictures online.

Sherri · United States · OpticBatch & MetaForge Reviewed Browse the full catalog

Quotes are shown with customer permission; names and locations appear as reviewers provided them.

Our Core Moat

Engineered to respect your system boundaries.

System Resource Monitor (Idle State Comparison)
Automata Labs low idle memory footprint compared to generic Electron applications

Lightweight Native Stack

Compiled Rust core wrapped inside an optimized Tauri shell. No heavy background node loops or duplicate Chromium engines cooking your memory footprint (<25MB idle RAM).

100% Local-First Privacy

Executes entirely on-device with full offline isolation. Absolute zero background telemetry policies, no metrics aggregation, and zero mandatory cloud-sync accounts.

Perpetual Fallback Licenses

Pay a single, clear one-time purchase price. Own your specific native software utility execution tier permanently without artificial subscription paywalls or ongoing usage tax.

Head-to-head

How MetaForge compares

Feature MetaForge FFmpeg + ExifTool scripts Online metadata strippers
Batch-normalize thousands of extracted frames ✓ Scripted Upload limits
Preview every change before writing ✓ — —
Runs locally, nothing uploaded ✓ ✓ —
No command line required ✓ — ✓
Strip artifacts or stamp intentional fields ✓ Per-file flags Strip only
One-time purchase, no subscription ✓ Free CLI Subscription

FAQ

Straight answers—no glossary dump

Why does my FFmpeg-extracted frame have different metadata than the video?

Because a video stores its metadata — capture time, camera make and model, GPS — at the container level, while the individual frames are just decoded pixels. When FFmpeg writes a still to JPEG, it creates a brand-new image file stamped with its own encoder and software tags and a generic or empty timestamp. None of the parent clip’s container fields carry over automatically, so the extracted frame and the source video describe themselves very differently.

Can't I just make FFmpeg copy the video's metadata onto the frames?

You can try FFmpeg’s -map_metadata option, but for still-image output it is unreliable: container tags like GPS, camera model, and original capture time rarely map cleanly into JPEG EXIF, and the result varies between FFmpeg builds and source formats. For consistent, predictable frames it is far more reliable to set the metadata you actually want on the extracted stills afterward. MetaForge does exactly that across the whole folder in one batch, with a preview before anything is written.

Does MetaForge re-compress or change the image?

No. Editing metadata is not the same as re-encoding pixels. MetaForge writes or removes the embedded fields — software tags, EXIF, IPTC, and XMP — without forcing another lossy pass, so the frame’s image data stays exactly as FFmpeg produced it unless you choose to re-encode it somewhere else.

Is this safe for sensitive, legal, or newsroom material?

Yes. MetaForge runs entirely on your Windows machine with no uploads and no telemetry, so frames never pass through a third-party site just to have their metadata cleaned. Every batch is previewed with a Simulation Report before it runs, and you can keep the originals by copying instead of overwriting, which helps with review and chain-of-custody clarity.

Do I need a subscription or an account?

No. MetaForge is a one-time purchase on the Microsoft Store for Windows 11 and Windows 10. It runs offline, needs no account, and collects no telemetry. You can process a handful of frames or tens of thousands with the same local Rust engine, and the license is yours to keep.

Related pages

RawTherapee batch export metadata scrub folder without a script and a prayer. Your pixels are public. Your location should not be. PowerPoint exported slide PNG metadata review batch before the file reaches a client. Windows Snipping Tool PNG strip metadata before documentation before you share a single file.

Scrub the invisible.
Route the unmanageable.

MetaForge is a native control panel for EXIF cleanup, sensitive metadata stripping, and high-throughput library routing—local cores, one-time purchase, no cloud upload queue.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Get it from Microsoft

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Open full product page

Technical specifications

Technical specifications for procurement

Spec Implementation
Data Sovereignty 100% on-device EXIF/IPTC reads and writes; no upload pipeline for core metadata workflows
Telemetry Status Disabled; no analytics SDK in shipping builds
Core Runtime Rust engine with native macOS and Windows file I/O
Network Requirements Fully functional offline after install
Deployment Compatibility macOS (Apple Silicon + Intel); Windows via Microsoft Store and direct purchase
Supported formats JPEG, PNG, TIFF, HEIC (read), WebP, and common camera RAW sidecars
Licensing Perpetual one-time purchase; platform policy applies