Folder → zip
Drop multiple, get back a zip. Originals untouched.
Most "free image resizer" sites are an upload form on top of a server-side ImageMagick wrapper, capped at 25 MB, throttled by daily quota, surrounded by ad inventory. The math itself — Lanczos, Bicubic, Nearest — is solved and has been for decades. Morph runs the resamplers via Canvas directly in your browser tab. Type the exact pixel dimensions, lock the aspect ratio, pick the algorithm that fits the source. No upload, no quota. Free for everything that runs on your device; AI is paid in credits.
Lanczos for photos: sharp edges, fewer ringing artifacts. Bicubic for graphics with mid-frequency detail. Nearest for pixel art so blocks stay blocky. The algorithm matters more than people realize, and Morph defaults to Lanczos because it's right for the most common case.
Type the numbers, lock or unlock aspect ratio, hit resize. Numerical readouts in DM Mono — precision-tool grade.
Drop multiple, get back a zip. Originals untouched.
No upload, no quota.
Resizing is a solved problem. The math is in every graphics library written since 1990. The reason a thousand "free image resizer" sites exist is that uploading-to-a-server is a freemium funnel: cap free users at 25 MB or 5 conversions per session, queue when traffic is heavy, run banner ads, and sell a monthly plan to escape. Same playbook at every one of them. The better ones handle the math beautifully but force a web upload anyway. Morph runs Canvas-based resampling directly in your browser tab.
If you're processing tens of thousands of files daily through a CMS pipeline, server-side tools with retry queues are correct. Morph is for the daily-driver path — drop a folder, set the target, download.
No. Morph resizes images locally in your browser using Canvas 2D and Web APIs. The file never leaves your device.
Lanczos is a resampling algorithm that preserves more detail when downsizing than the default bilinear browsers use for img tags. For photos, the difference is visible — sharper edges, fewer ringing artifacts. Morph defaults to Lanczos because it is the right call for the most common case.
Yes. Drop multiple files onto the drop zone and Morph resizes them in parallel using the same target dimensions or percentage. The output is a zip with the originals' filenames preserved.
Almost always, yes — fewer pixels to encode means a smaller file. But the encoding format also matters. Resizing a JPG keeps it a JPG with the same compression settings; converting to WEBP at the same time gets you another big size drop.
Practical limit is around 16,000 pixels on the longer edge. Above that, browser canvas memory becomes the limit. For very large source images, downsize in two passes.
PNG and WEBP outputs preserve alpha channels through the resize. JPG outputs do not — JPG does not support transparency, so transparent regions become white.