ExifCleaner: baixar versions anteriors

ExifCleaner 4.5.0
ExifCleaner 4.5.0 cleans PNG and JPEG files with the app's own built-in cleaner when Save as copy is on, fixes WebP resolution loss in that same mode, and removes JPEG content credentials to match what the bundled ExifTool already removed.
What's new
- PNG and JPEG copies are now cleaned by the app's own built-in cleaner. With Save as copy on, PNG and JPEG files are cleaned by a built-in cleaner instead of the bundled ExifTool, whenever it supports every preservation setting you have turned on. Files it declines to handle are cleaned by ExifTool exactly as before. Every cleaned copy is reopened and checked by ExifTool for leftover metadata before it is kept; if the check finds anything unexpected, the copy is discarded, your original file is left untouched, and the file is reported as failed. Cleaning many PNG or JPEG files as copies in one batch now costs a few extra milliseconds per file from that check measured at about +5.9 ms per JPEG and +6.6 ms per PNG on a development machine which was judged worth paying so a copy with leftover metadata is never silently kept.
- WebP now keeps its resolution with Save as copy on. With Preserve resolution on, WebP files are cleaned by ExifTool and keep their resolution. This removes the 4.4.0 known limitation that WebP resolution was never kept in that mode.
- JPEG content credentials (C2PA) are now removed. Content credential data carried in JPEG APP11 segments is now removed by the built-in cleaner, matching what ExifTool already removed.
Other changes
- A failing PNG or JPEG copy now reports a generic "Generated output write failed" message instead of ExifTool's own more specific error text, matching the message every other copy-mode format (RAW, TIFF, media and WebP) already shows on a failed write.
Known limitations in 4.5.0
No executable release-blocking known gaps are approved for this release; documented format constraints follow below.
Format constraints
- TIFF: only the first page of a multi-page TIFF is cleaned; later pages keep their own ImageDescription, Software, Artist and Copyright. HostComputer, DocumentName and CameraSerialNumber also remain on the first page.
- RAW: some Canon maker-note tags stay because ExifTool cannot delete them (for example the CR2 maker-note SerialNumber). The RAW fix was measured on CR2, CR3, DNG and RW2 samples; no claim is made for ARW, NEF, ORF, PEF or SRW. RAF cleaning is still refused and the source is left unchanged.
- Time limits: a write's limit is 30 seconds plus one second per 20 MB of the file. 20 MB per second is an assumed floor for slow disks, not a measured speed. With Save as copy off, for formats ExifTool rewrites in place such as JPEG and PNG, a stop that lands just after ExifTool replaced the original leaves the original cleaned even though the app reports a failure.
- PDF: ExifTool uses reversible updates, so prior metadata may remain recoverable.
- MKV: unsupported because ExifTool does not expose a writable removal path.
- AVIF: user-reported partial-removal behavior remains under investigation.
Rollback
If a 4.5.0 PNG or JPEG copy looks wrong, reinstall 4.4.0 from the releases page. The built-in cleaner introduced in 4.5.0 is used only when Save as copy is on, and only when it supports every preservation setting you have turned on; with Save as copy off, ExifTool cleans the file exactly as it did in 4.4.0, so that mode is unaffected by this rollback. Your settings carry over unchanged. Reinstalling 4.4.0 also gives up the 4.5.0 WebP-resolution fix.
For maintainers: remove the format's handler from HANDLERS (exifcleaner-node/src/admission/registry.ts), publish an exifcleaner-node patch, and bump the app's exact pin. The format then declines as unsupported-format before any write and the app routes it to ExifTool proven by tests/integration/native_copy_routing.test.ts's "a format absent from the real capability table (as after removing its HANDLERS entry) is cleaned by ExifTool with zero native calls" and

ExifCleaner 4.4.0
ExifCleaner 4.4.0 removes metadata that earlier versions left behind in comments, TIFF and RAW files, keeps a cleaned file's print resolution, and recovers from writes that run past their time limit.
Fixes
- Files whose only metadata was a comment are now cleaned. A file whose only removable metadata was a free-text comment, such as a JPEG comment, was reported as having no removable metadata and skipped. It is now counted and the comment is removed. The same comment field was measured on GIF and RW2 files.
- TIFF: descriptive and camera tags are removed from the first page (#199). ImageDescription, Make, Model, Software, ModifyDate, Artist, Copyright, Rating and the Windows XP title, comment, author, keyword and subject tags no longer survive a default clean. Image data is unchanged, and TIFF writes now go through the staged, verified output path in both modes, so a failed write leaves the original untouched.
- RAW: identifying metadata is removed. CR2, CR3, DNG, RW2 and the other supported RAW formats no longer keep identifying text, camera body and lens serial numbers, owner names, the DNG raw-data ID and original raw file name, or capture dates and time offsets that ExifTool can delete. Make, Model and the DNG camera and color tags are kept, and the image data is unchanged.
- Writes that run past their time limit are stopped cleanly. The app stops that ExifTool write, removes the partial output it left, and cleans the remaining files in the batch on a fresh ExifTool session. If the partial output cannot be removed, the file's row shows where it is.
New: Preserve resolution
A Preserve resolution setting, on by default, keeps a cleaned file's print resolution (DPI) exactly as the source recorded it: JPEG JFIF and EXIF resolution, and PNG pHYs. Printed sizes no longer change. GPS, author, software and comment metadata are still removed. Existing settings pick it up turned on after upgrading. Turning it off restores the previous behavior of removing resolution too.
Other changes
- The Windows portable download is renamed to ExifCleaner.4.4.0.portable.exe, so it can be told apart from the installer by filename alone (#261).
- Files larger than 4 GB have been cleaned successfully since 4.0.0, because ExifTool 12.88 made large-file support its default. 4.4.0 adds a regression test so a future ExifTool update cannot silently bring the old failure back. This is verification, not a new fix.
- A 4.0.0 changelog entry that claimed macOS code signing and notarization was corrected. Releases are unsigned by explicit maintainer policy (#362).
Known limitations in 4.4.0
No executable release-blocking known gaps are approved for this release; documented format constraints follow below.
Format constraints
- TIFF: only the first page of a multi-page TIFF is cleaned; later pages keep their own ImageDescription, Software, Artist and Copyright. HostComputer, DocumentName and CameraSerialNumber also remain on the first page.
- RAW: some Canon maker-note tags stay because ExifTool cannot delete them (for example the CR2 maker-note SerialNumber). The RAW fix was measured on CR2, CR3, DNG and RW2 samples; no claim is made for ARW, NEF, ORF, PEF or SRW. RAF cleaning is still refused and the source is left unchanged.
- WebP: with Save as copy on, the built-in WebP cleaner does not keep resolution, whether Preserve resolution is on or off.
- Time limits: a write's limit is 30 seconds plus one second per 20 MB of the file. 20 MB per second is an assumed floor for slow disks, not a measured speed. With Save as copy off, for formats ExifTool rewrites in place such as JPEG and PNG, a stop that lands just after ExifTool replaced the original leaves the original cleaned even though the app reports a failure.
- PDF: ExifTool uses reversible updates, so prior metadata may remain recoverable.
- MKV: unsupported because ExifTool does not expose a writable removal path.
- AVIF: user-reported partial-removal behavior remains under investigation.

ExifCleaner 4.3.0
ExifCleaner 4.3.0 routes WebP metadata removal through a new native engine, and stops a benign ExifTool warning from being reported as a failed inspection.
Native WebP handling
- WebP files are now cleaned by a native engine rather than by shelling out to ExifTool. The native path is used only when it reports the capability for the exact request; anything it declines falls back to the existing ExifTool path.
- Every native write goes through a staged, verified publication. The cleaned result is written to a private staging location, verified, and only then published over the original. A write that cannot be verified does not replace your file.
- Uncertain processing preserves the source. If the native path fails in a way that is not provably safe to retry, the source file is left unchanged rather than being replaced by a partially processed result.
Fixes
- Benign ExifTool [minor] warnings no longer fail metadata display (#344). Files that cleaned correctly but produced a non-fatal warning previously surfaced as an inspection failure.
Known limitations in 4.3.0
No executable release-blocking known gaps are approved for this release; documented format constraints follow below.
Format constraints
- RAF: cleaning is refused and the source is left unchanged because a safe cleaned RAF artifact cannot currently be guaranteed.
- PDF: ExifTool uses reversible updates, so prior metadata may remain recoverable.
- MKV: unsupported because ExifTool does not expose a writable removal path.
- TIFF and AVIF: user-reported partial-removal behavior remains under investigation.
Downloads
──────────────────────────────┬────────────────────────────
Platform │File
──────────────────────────────┼────────────────────────────
Windows portable (recommended)│ExifCleaner.4.3.0.exe
──────────────────────────────┼────────────────────────────
Windows installer │ExifCleaner.Setup.4.3.0.exe
──────────────────────────────┴────────────────────────────
Verify downloads against the release's SHASUMS256.txt file.
Opening unsigned builds
ExifCleaner remains unsigned. Signing would require publishing the maintainer's verified legal identity; no signed build is being promised.
- Windows: if SmartScreen appears, choose More info → Run anyway after verifying the checksum.
Every artifact is built publicly from tagged source by GitHub Actions. ExifCleaner makes no network requests during normal use.
Only download ExifCleaner from the GitHub releases page.
Full changelog: https://github.com/szTheory/exifcleaner/compare/v4.2.1...v4.3.0

ExifCleaner 4.2.1
ExifCleaner 4.2.1 makes the supported-format promise match what the bundled metadata engine can safely process.
Format support
- M4A is now supported. Audio metadata is removed through the same staged, verified publication path used by other media files.
- MKV is no longer accepted. ExifTool can read Matroska metadata but cannot write MKV files, so rejecting the format before processing is the truthful behavior.
- The README now lists the app's exact intake allowlist instead of ExifTool's much broader catalog, and CI prevents that list from drifting from source.
- DOCX remains unsupported.
The patch includes a metadata-bearing M4A fixture, explicit MKV rejection coverage, and installed-artifact M4A smoke coverage.
Known limitations in 4.2.1
No executable release-blocking known gaps are approved for this release; documented format constraints follow below.
Format constraints
- RAF: cleaning is refused and the source is left unchanged because a safe cleaned RAF artifact cannot currently be guaranteed.
- PDF: ExifTool uses reversible updates, so prior metadata may remain recoverable.
- MKV: unsupported because ExifTool does not expose a writable removal path.
- TIFF and AVIF: user-reported partial-removal behavior remains under investigation.
Downloads
──────────────────────────────┬────────────────────────────
Platform │File
──────────────────────────────┼────────────────────────────
Windows portable (recommended)│ExifCleaner.4.2.1.exe
──────────────────────────────┼────────────────────────────
Windows installer │ExifCleaner.Setup.4.2.1.exe
──────────────────────────────┴────────────────────────────
Verify downloads against the release's SHASUMS256.txt file.
Opening unsigned builds
ExifCleaner remains unsigned. Signing would require publishing the maintainer's verified legal identity; no signed build is being promised.
- Windows: if SmartScreen appears, choose More info → Run anyway after verifying the checksum.
Every artifact is built publicly from tagged source by GitHub Actions. ExifCleaner makes no network requests during normal use.
Only download ExifCleaner from the GitHub releases page.
Full changelog: v4.2.0...v4.2.1

ExifCleaner 4.2.0
ExifCleaner 4.2.0 makes the first run calmer and keeps the packaged privacy toolchain current without adding background network activity.
A clearer first run
- The empty intake is now centered as one responsive composition instead of feeling split between copy and controls.
- Choose files is the clear primary action, with Choose folder available beside it and drag and drop unchanged.
- The intake explains whether ExifCleaner will save cleaned copies or modify originals, using the current setting rather than a generic promise.
- Nested folder intake reports unsupported files and folders it could not read instead of silently losing that summary.
- Help now includes New Releases, which opens the GitHub Releases page only when you click it. ExifCleaner does not poll for updates.
Localization with provenance
- Romanian is now fully supported. The 70 strings contributed in PR #297 are preserved exactly and credited to their contributor.
- Every supported locale covers the first-run and New Releases vocabulary.
- Translation records now distinguish existing community work from assisted drafts, track the English source each string translates, and expose stale or missing work without silently overwriting it.
Runtime and release maintenance
- The bundled ExifTool is updated from 13.50 to 13.59 for Unix and 32-bit-compatible Windows packages, with pinned upstream SHA-256 verification.
- Packaged Electron disables RunAsNode, NODE_OPTIONS, and Node CLI inspection. Cookie encryption remains disabled because ExifCleaner does not need cookie storage.
- Release automation treats a verified already-published version as a quiet no-op while retaining the full evidence gates for a new release.
Known limitations in 4.2.0
No executable release-blocking known gaps are approved for this release; documented format constraints follow below.
Format constraints
- RAF: cleaning is refused and the source is left unchanged because a safe cleaned RAF artifact cannot currently be guaranteed.
- PDF: ExifTool uses reversible updates, so prior metadata may remain recoverable.
- MKV: ExifTool does not expose a complete writable removal path.
- TIFF and AVIF: user-reported partial-removal behavior remains under investigation.
Downloads
──────────────────────────────┬────────────────────────────
Platform │File
──────────────────────────────┼────────────────────────────
Windows portable (recommended)│ExifCleaner.4.2.0.exe
──────────────────────────────┼────────────────────────────
Windows installer │ExifCleaner.Setup.4.2.0.exe
──────────────────────────────┼────────────────────────────
macOS (Apple Silicon) │ExifCleaner-4.2.0-arm64.dmg
──────────────────────────────┼────────────────────────────
macOS (Intel) │ExifCleaner-4.2.0.dmg
──────────────────────────────┼────────────────────────────
Linux (AppImage) │ExifCleaner-4.2.0.AppImage
──────────────────────────────┼────────────────────────────
Linux (Debian/Ubuntu) │exifcleaner_4.2.0_amd64.deb
──────────────────────────────┼────────────────────────────
Linux (Fedora/RHEL) │exifcleaner-4.2.0.x86_64.rpm
──────────────────────────────┴────────────────────────────
Verify downloads against the release's SHASUMS256.txt file.
Opening unsigned builds
ExifCleaner remains unsigned. Signing would require publishing the maintainer's verified legal identity; no signed build is being promised.
- macOS 14 and earlier: right-click or Control-click the app, choose Open, then choose Open again.
- macOS 15 and later: open the app once, then use System Settings → Privacy & Security → Open Anyway.
- Windows: if SmartScreen appears, choose More info → Run anyway after verifying the checksum.
- Linux: make the AppImage executable with chmod +x ExifCleaner-4.2.0.AppImage; .deb and .rpm packages install normally.
Every artifact is built publicly from tagged source by GitHub Actions. ExifCleaner makes no network requests during normal use.
Only download ExifCleaner from the GitHub releases page.
Full changelog: https://github

ExifCleaner 4.1.0
ExifCleaner 4.1.0 makes batch cleaning safer to understand and harder to misread.
Clearer results
- Each file now reports what actually happened: metadata removed, already clean, unchanged, or refused.
- Metadata details open with removed fields visible immediately. Fields that remain are kept in one secondary disclosure.
- Files can be sorted by name, type, source size, and before/after metadata counts while folder groups stay intact.
- The size column shows the original and resulting sizes instead of implying they are the same value.
Safer processing
- New installs default to Save as copy. Existing preferences are preserved during migration.
- RAF files are refused without writing because ExifTool cannot safely produce the requested cleaned RAF artifact. The rest of the batch continues.
- Already-clean files avoid an unnecessary rewrite. When macOS attribute removal is requested, only that requested operation runs.
- MP4 and MOV processing now explicitly clears movie, track, and media create/modify dates and verifies the generated artifact before success.
- File paths containing carriage returns or line feeds are rejected at both the IPC and ExifTool boundaries.
Easier intake and navigation
- Native Choose files and Choose folder actions complement drag and drop.
- Unsupported files are summarized once instead of disappearing silently.
- The drop area shows whether output will be written as cleaned copies or in place.
- Filenames and paths display safely in right-to-left locales, and Vietnamese now uses the standard vi locale code.
Engineering and contributor experience
- Electron, Vite, Vitest, Playwright, and electron-builder were upgraded within the supported Node 22 toolchain.
- CI and release workflows use pinned actions, explicit permissions and timeouts, deterministic runners, and a fixed seven-artifact release inventory.
- The Homebrew workflow is now read-only; third-party tap updates remain an explicit maintainer action.
- Architecture, code-walkthrough, subsystem, translation, and contribution guides are now maintained in the repository with automated drift checks.
Known limitations in 4.1.0
No executable release-blocking known gaps are approved for this release; documented format constraints follow below.
Format constraints
- RAF: cleaning is refused and the source is left unchanged because a safe cleaned RAF artifact cannot currently be guaranteed.
- PDF: ExifTool uses reversible updates, so prior metadata may remain recoverable.
- MKV: ExifTool does not expose a complete writable removal path.
- TIFF and AVIF: user-reported partial-removal behavior remains under investigation.
Downloads
──────────────────────────────┬────────────────────────────
Platform │File
──────────────────────────────┼────────────────────────────
Windows portable (recommended)│ExifCleaner.4.1.0.exe
──────────────────────────────┼────────────────────────────
Windows installer │ExifCleaner.Setup.4.1.0.exe
──────────────────────────────┼────────────────────────────
macOS (Apple Silicon) │ExifCleaner-4.1.0-arm64.dmg
──────────────────────────────┼────────────────────────────
macOS (Intel) │ExifCleaner-4.1.0.dmg
──────────────────────────────┼────────────────────────────
Linux (AppImage) │ExifCleaner-4.1.0.AppImage
──────────────────────────────┼────────────────────────────
Linux (Debian/Ubuntu) │exifcleaner_4.1.0_amd64.deb
──────────────────────────────┼────────────────────────────
Linux (Fedora/RHEL) │exifcleaner-4.1.0.x86_64.rpm
──────────────────────────────┴────────────────────────────
Verify downloads against the release's SHASUMS256.txt file.
Opening unsigned builds
ExifCleaner remains unsigned. Signing would require publishing the maintainer's verified legal identity; no signed build is being promised.
- macOS 14 and earlier: right-click or Control-click the app, choose Open, then choose Open again.
- macOS 15 and later: open the app once, then use System Settings → Privacy & Security → Open Anyway.
- Windows: if Smar

ExifCleaner 4.0.1
ExifCleaner 4.0.1 is a focused data-safety and release-reliability update.
Data safety
- Save as copy now preserves the original. The app writes to the actual collision-safe _cleaned path and Reveal follows that returned path.
- RAW files always use a copy. Supported RAW formats never overwrite the submitted original, even when Save as copy is disabled.
- RAW and video output is verified before success. Failed generated output is removed instead of being reported as complete.
Privacy
- Remove macOS attributes is now connected to the processing path. When enabled, it clears extended attributes from the artifact that was actually written.
- The macOS attribute command now passes filenames as fixed arguments rather than through a shell.
Release reliability
- Installed builds now exercise the save-as-copy and advertised-format contracts on macOS, Windows, and Linux before release artifacts are accepted.
- Release notes must match the package version, known gaps must remain machine-readable, and two-part internal tags are rejected from the public release namespace.
- The release also includes the previously unreleased SIZE display, settings icon, PDF fixture, per-launch test-profile, and release-gate fixes from #300, #301, #305, #306, and #292.
Known limitations in 4.0.1
- Impact: A cleaned MP4 may still include original create-date metadata values.
Scope: MP4 files with QuickTime CreateDate, TrackCreateDate, or MediaCreateDate values processed through ExifCleaner 4.0.0 or 4.0.1
Workaround: For sensitive MP4s, run ExifTool manually with -CreateDate= -TrackCreateDate= -MediaCreateDate= after cleaning, then verify those tags are absent.
Target fix: 4.1.0.
Issue: #240
See the README's known limitations by format before relying on irreversible removal from PDF or MKV files.
Downloads
──────────────────────────────┬────────────────────────────
Platform │File
──────────────────────────────┼────────────────────────────
Windows portable (recommended)│ExifCleaner.4.0.1.exe
──────────────────────────────┼────────────────────────────
Windows installer │ExifCleaner.Setup.4.0.1.exe
──────────────────────────────┼────────────────────────────
macOS (Apple Silicon) │ExifCleaner-4.0.1-arm64.dmg
──────────────────────────────┼────────────────────────────
macOS (Intel) │ExifCleaner-4.0.1.dmg
──────────────────────────────┼────────────────────────────
Linux (AppImage) │ExifCleaner-4.0.1.AppImage
──────────────────────────────┼────────────────────────────
Linux (Debian/Ubuntu) │exifcleaner_4.0.1_amd64.deb
──────────────────────────────┼────────────────────────────
Linux (Fedora/RHEL) │exifcleaner-4.0.1.x86_64.rpm
──────────────────────────────┴────────────────────────────
Verify downloads against the release's SHASUMS256.txt file.
Windows security checks
- Windows portable (recommended): ExifCleaner.4.0.1.exe — SHA-256 7375676a911fccefd4d2731621bf9d815932153750d7b900e6e8ecec48028f12; VirusTotal report; submitted to Microsoft for malware analysis on 2026-08-02.
- Windows installer: ExifCleaner.Setup.4.0.1.exe — SHA-256 ad77fe49f2e58d6df153e1a841ad784e15cef2d6a7bc38b771b89fb0d0a7bac4; VirusTotal report; submitted to Microsoft for malware analysis on 2026-08-02.
These unsigned artifacts may still trigger reputation-based warnings. The links above identify the exact release bytes; they are not a promise that every scanner reports zero detections.
Opening unsigned builds
ExifCleaner remains unsigned. Signing would require publishing the maintainer's verified legal identity; no signed build is being promised.
macOS
- macOS 14 (Sonoma) and earlier: right-click or Control-click the app, choose Open, then choose Open again.
- macOS 15 (Sequoia) and later: open the app once, then use System Settings → Privacy & Security → Open Anyway.
Windows
The portable build is the primary Windows download. If SmartScreen displays “Windows protected your PC,” choose More info → Run anyway after verifying the checksum.
Linux
Make the AppImage executable with 

The first major release in 5 years — a complete rebuild from the ground up. Same privacy-first philosophy, everything else modernized.
Highlights
New Privacy Controls
- Preserve photo orientation — Photos stay upright after cleaning (enabled by default)
- Save as copy — Create a _cleaned copy instead of overwriting the original
- Preserve timestamps — Keep original file dates intact
- Preserve color profile — Retain ICC color data for accurate colors
- Remove macOS extended attributes — Strip quarantine and Spotlight metadata (macOS only)
All toggleable from the new Settings panel.
Folder Support
Drop an entire folder and ExifCleaner processes every supported file inside, recursively.
Metadata Inspector
Click any processed file to see exactly which metadata tags were removed — a full before/after diff.
25 Languages
Now available in 25 languages with in-app language switching — no need to change your system locale.
New since v3.6.0: Catalan, Croatian, Czech, Danish, Hungarian, Malayalam, Persian, Polish, Portuguese (Brazil), Slovak, Swedish, Turkish, Vietnamese
Redesigned Interface
- Modern React-based UI with a clean design system
- Dark mode that follows your system preference (or override manually)
- Settings drawer with all options in one place
- Status bar showing progress, file counts, and tags removed
Under the Hood
- Electron 35 (up from 11) — 5 years of Chromium security patches
- Sandboxed renderer — the UI process has zero access to your filesystem or system
- IPC validation — all internal communication validated with schemas
- Smaller bundle — ~35 MB on macOS
- Automated CI/CD — every commit tested across macOS, Windows, and Linux
- SHA-256 checksums included for all downloads
What hasn't changed
- Zero network traffic — no telemetry, no auto-update, no phone home. Ever.
- Fast — hundreds of files processed in seconds
- Open source — MIT license
Downloads
─────────────────────┬────────────────────────────
Platform │File
─────────────────────┼────────────────────────────
macOS (Apple Silicon)│ExifCleaner-4.0.0-arm64.dmg
─────────────────────┼────────────────────────────
macOS (Intel) │ExifCleaner-4.0.0.dmg
─────────────────────┼────────────────────────────
Windows (installer) │ExifCleaner.Setup.4.0.0.exe
─────────────────────┼────────────────────────────
Windows (portable) │ExifCleaner.4.0.0.exe
─────────────────────┼────────────────────────────
Linux (AppImage) │ExifCleaner-4.0.0.AppImage
─────────────────────┼────────────────────────────
Linux (Debian/Ubuntu)│exifcleaner_4.0.0_amd64.deb
─────────────────────┼────────────────────────────
Linux (Fedora/RHEL) │exifcleaner-4.0.0.x86_64.rpm
─────────────────────┴────────────────────────────
Verify your download: check SHASUMS256.txt against the file you downloaded.
Opening unsigned builds
ExifCleaner is not code-signed. Your OS will warn you on first launch. This is
expected and is a one-time step per platform.
macOS
- macOS 14 (Sonoma) and earlier: right-click (or Control-click) the app → Open →
click Open in the dialog.
- macOS 15 (Sequoia) and later: right-click → Open no longer works. Double-click the
app once and let it be blocked, then open System Settings → Privacy & Security,
scroll down, and click Open Anyway next to the ExifCleaner message.
Windows
Windows Defender SmartScreen shows "Windows protected your PC". Click More info →
Run anyway.
Linux
No gatekeeping. Make the AppImage executable with chmod +x ExifCleaner-4.0.0.AppImage.
.deb and .rpm install normally:
sudo apt install ./exifcleaner_4.0.0_amd64.deb # Debian/Ubuntu
sudo dnf install ./exifcleaner-4.0.0.x86_64.rpm # Fedora/RHEL
Why isn't it signed?
macOS signing requires an Apple Developer certificate at $99/year, and that certificate
embeds the holder's legal name, which macOS displays in the Gatekeeper dialog.
Windows requires a separate EV certificate at $200–600/year tied to a verified legal
identity. For a privacy tool maintained anonymously, that isn't a tradeoff this project
is willing to make.

Security
- Fix for XSS and Electron reverse shell vulnerabilities by sanitizing exiftool HTML output in the UI.
To take advantage of this, an attacker would have had to write image metadata containing malicious script code to a file that you then download and run through ExifCleaner.
Proofs of concept: