MediaCleaner Pro is designed to go from download to first run in under two minutes. There is no installer, no dependency to resolve, and no account to create. The steps below walk you through downloading the binary, pointing it at your images, and launching the web UI to kick off your first cleaning job.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/xcoder-es/media-cleaner-pro/llms.txt
Use this file to discover all available pages before exploring further.
Download the binary
Grab the binary for your platform from the GitHub Releases page.
On macOS and Linux, mark the binary as executable after downloading:
| Platform | File |
|---|---|
| Windows x86_64 | mediacleaner-pro-windows-x86_64.exe |
| macOS Apple Silicon | mediacleaner-pro-macos-aarch64 |
| macOS Intel | mediacleaner-pro-macos-x86_64 |
| Linux x86_64 | mediacleaner-pro-linux-x86_64 |
Run the binary
Execute the binary from the directory where you want MediaCleaner Pro to store its configuration and database.On the first run, MediaCleaner Pro automatically:
- Creates a
.envconfiguration file in the current directory - Creates the default input directory at
data/source/ - Creates the default output directory at
data/output/ - Initialises a SQLite database at
mediacleaner.db
Add your images
Copy or move the images you want to process into the Alternatively, if your images are already organised elsewhere on disk, open the Restart the binary after editing
data/source/ directory that was created in the previous step..env file and update the SOURCE_DIR variable to point at that directory instead of copying files:.env for the change to take effect.Open the web UI
With the binary running, navigate to the embedded web interface in any modern browser:The UI loads directly from the binary — no network connection or CDN is involved.
Configure and start a run
In the web UI you can review and adjust the source and destination directories and the Hamming threshold before starting. When you are ready, click Start.MediaCleaner Pro will progress through all ten pipeline stages and stream live status updates back to the browser. You can pause, resume, or cancel the run at any time using the controls at the top of the UI.
Output Directory Structure
After a completed run, processed files are organised under your configuredDEST_DIR (default data/output/) using the following layout: