Image Resizer: Choice of Mode, Lock, and Batch Order
The four decisions that decide whether a resize is clean or distorted, and the order of operations that keeps quality intact.
1. Percentage Mode versus Pixel Mode
Percentage mode scales an image relative to its own dimensions, so every photo in a batch resizes by the same factor regardless of starting size. Pixel mode sets exact width and height in pixels for every output. Percentage is the right choice for a batch where the originals have different sizes; pixel mode is the right choice when every output must satisfy a single fixed image specification.
Mixing the two is a common mistake. A batch where some images come out 50 percent smaller and others come out 800 pixels wide produces a folder of outputs that share none of the size relationships the originals did. Pick the mode before you add the files, not after.
3. Aspect Ratio Locking and Why Unlocking Distorts
Aspect ratio is the ratio of width to height of an image. A lock that keeps the ratio intact derives the missing dimension from the original, so resizing width to 800 pixels automatically rescales height proportionally. Unlocking the lock lets you set both dimensions freely, which immediately distorts the photo unless you explicitly intend the squash.
A useful middle ground is the max-dimension cap, which sets a ceiling on the longest edge of the output and rescales both width and height down proportionally while preserving the aspect ratio. This is the cleanest way to produce uniformly web-ready images from a batch of mixed orientations.
2. Quality Settings and the Compression Penalty
Resize operations on JPEG files should always expose a quality setting between 1 and 100. The resize itself keeps the original pixel data balanced across the new dimensions, but the recompression at save time is what actually shrinks the byte size. Quality 75 produces a visually transparent output for most photographic content and roughly halves the file size compared to quality 95.
PNG outputs have no quality knob because PNG is lossless, so resize in PNG when you need pixel-perfect results and in JPEG or WebP when file size matters more than pixel fidelity. WebP at quality 80 typically outperforms JPEG quality 75 in visual quality and file size, and modern browsers render it everywhere.
4. Privacy and Why Local Resize Outperforms Hosted
Resizing in the browser through the HTML5 Canvas API keeps every photo on the local device. Upload-based services send your photos off, process them on a remote server, and send them back. That round trip exposes your image content, costs seconds per image, and only works while you have a working internet connection.
Local resize scales to batches of dozens or hundreds of images instantly, runs as smoothly offline as online, and never logs a single byte of your photo content. Choose a tool that does the work without taking the upload when the option exists.
Clean Resizes, No Distortion
Image resizing is one of the most common tasks in a content workflow, and a few quick decisions decide whether the outputs are clean or distorted. ToolWise Free Online Image Resizer runs entirely in your browser, supports percentage and pixel modes, locks aspect ratios, caps max dimensions, and never uploads your photos. Drop your batch, pick your mode, and export.