Crop to exact pixels, resize while preserving aspect ratio, and re-encode to PNG, JPEG or WebP without uploading. Built for quick screenshot and asset prep in the browser canvas path.
Enforced limits
| Constraint |
Value |
| Input bytes |
≤ 20 MB |
| Pixel count |
≤ 16,000,000 |
| Max side |
≤ 8192 |
Failed validation shows a reason and blocks export. Crop rectangles must be integer pixels fully inside the source.
Verified geometry
For an 800×600 source, the square preset yields crop {x:100,y:0,width:600,height:600}. Resizing that 800×600 frame to width 400 yields {width:400,height:300}. Height-based resize mirrors the same ratio math.
Suggested order of operations
- Select a file under the limits.
- Apply a aspect preset or manual crop.
- Set output width or height and confirm the paired dimension.
- Choose PNG (UI/transparency), JPEG (photos) or WebP (web delivery) and quality.
- Download once from the original—avoid repeated lossy re-encodes.
Crop out personal data before sharing. EXIF-heavy print pipelines may still need a dedicated metadata tool.
Choosing an output codec
PNG preserves sharp UI edges and transparency but grows quickly on photos. JPEG suits continuous-tone photos and discards alpha. WebP often wins for web heroes if your audience browsers are modern—compare file sizes at two or three quality points before you commit.
Always start from the original asset. Re-encoding an already compressed JPEG multiplies artifacts. Crop first to the framing you need, then resize, then encode once.
Screenshots frequently contain names, emails or order IDs in the pixel buffer. Crop them out before you publish. Local processing does not mean the downloaded file is safe to upload everywhere. If you must strip EXIF GPS or camera serials for a compliance workflow, finish with a metadata-focused tool after export.
When a file fails validation, read the message: oversize bytes, oversize megapixels and non-integer crops are rejected up front so the canvas path never starts on an unsafe input.
Aspect presets in practice
Square crops help avatars and catalog tiles. 4:3 matches many older photo and slide formats. 16:9 fits blog heroes and video posters. Original leaves framing alone so you can resize without cutting. Centered math is predictable; for subject-aware crops you still need manual X/Y.
Output dimensions must stay positive integers within the 8192 and 16 MP caps. If you need a 4K-wide asset from a huge source, crop first to discard unused margins so the pixel budget is spent on the subject.
Name exported files with width and codec (hero-1280.webp) so later you can tell which derivative you are looking at without opening them all.
After export, open the file once in a clean viewer to confirm orientation and colors before you attach it to a ticket or CMS entry.
FAQ
Which formats are supported?
Inputs the browser can decode; outputs image/png, image/jpeg or image/webp.
What are the size limits?
20 MB input, 16 megapixels decode/output, 8192 px max per side.
Is the image uploaded?
No. Crop, resize and re-encode run locally.
What crop presets exist?
Original, square, 4:3 and 16:9, centered inside the source.