Resize a folder of images without any of them leaving the machine.
A resizer that does the tedious parts properly: reads what a camera actually produces, finds the border nobody wants to trim by hand, and hits a file size you name instead of a quality number you have to guess at.
Every image tool asks for a quality number. Nobody knows what 82 means.
What people actually have is a limit: this gallery takes 2 MB, this marketplace rejects anything over 5, this client wants 300 DPI and does not care how. File SDM takes the limit and finds the settings, resizing only when quality alone cannot get under the cap.
The rest is the work around the work. Scans arrive with a border. Phone shots arrive as HEIC that half the web still cannot read. A camera's RAW is sixty megabytes of something no marketplace accepts. Those are the steps that turn a five-minute job into an afternoon, and they are the steps this does.
What it does
Finds the border
Not just a solid colour. Scan edges, page backgrounds and text margins, detected per file and shown as a rectangle you can correct before anything is written.
Hits a size cap
Name a target in megabytes. It searches the quality settings for the one that lands under it, and only resizes when no quality setting will do.
Reads real cameras
RAW from Canon, Nikon and Sony. HEIC from a phone. AVIF, TIFF, animated GIF. The formats that actually turn up, not the three a web tool supports.
Removes watermarks
A mark at the edge is cropped away. One inside the picture is reconstructed from its surroundings — convincing on sky, wall or fabric, and worth checking over a face.
Upscales locally
Real-ESRGAN through whichever accelerator is present: TensorRT or CUDA on an NVIDIA card, DirectML on anything else, CPU when there is nothing else.
Asks a model when it is unsure
Geometry decides most crops. When two answers are equally defensible a local vision model arbitrates — and says so, rather than quietly guessing.
One folder
The whole application is one directory.
Including its Python interpreter. Nothing is written to the registry, to
%APPDATA%, or to a global package directory. Move it to another drive by
dragging it. Back it up by copying it. Remove it by deleting it.
That is not tidiness for its own sake: a security product asked to trust an app scattered across four profile subdirectories will ask again for every one of them. One folder is one exception.
├── app/ the window
├── engine/ the image pipeline
├── runtime/
│ ├── python/ its own interpreter
│ ├── cache/
│ └── appdata/ settings, presets
└── models/ weights, if you want them
Formats
Everything here can be read. The highlighted ones are the reason people give up on the browser-based tools and go looking for something that runs locally.
Where this actually stands
Built, not released. Four phases are written and the installer works — it downloads its own interpreter, installs into a folder you choose, and keeps its packages current from inside the app.
What it has not done is process a real batch end to end. Until it has, there is no download here, because handing someone an installer for something nobody has run in anger is how you find out what it does wrong at their expense instead of ours.