Input
- JPEG, PNG, and WebP images verified by file bytes
- Up to 12 files, 12 MiB each, and 96 MiB per batch
- Files stay in memory in the active browser tab
Image delivery
Images checked against your size and format limits, with missed targets clearly labeled.
Resize, crop, convert, target a file-size ceiling, and remove supported metadata in one ordered flow.
01
1. Add files
Choose or drop files after the local workspace opens.
02
2. Set the result
Choose the output format and limits after opening the workspace.
Processing plan
- Set delivery limits
- Process locally
- Verify and export
Save your settings on this device for reuse. Presets do not include files or their contents.
File controls load after an explicit action. Processing and downloads stay in this browser tab.
Worked example · Deliver one image to a portal with two independent limits
Worked example
Deliver one image to a portal with two independent limits
Suppose a portal accepts a 300 × 300 bounding box and at most 200000 bytes. Use a synthetic 600 × 400 image for rehearsal, then record the actual portal requirements. Dimensions, bytes, format and padding each need a separate decision.
- Input and settings
- 600 × 400 · box 300 × 300 · 200000-byte ceiling
- Expected output
- 300 × 200 · target 195 KiB = 199680 bytes
Steps to reproduce
Choose Fit within width and height, set 300 × 300, disable additional dimension reduction for this trial and choose 195 KiB or less for the byte target. Run one file first; review the verified dimensions and actual bytes before batching.
Check before you use it
A missed target is a result to review, not a successful submission. Try another accepted format or explicitly allow dimension reduction. For an exact square without cropping, use padding and check the background. The workflow does not guarantee that a portal will accept an otherwise valid file; check the recipient’s format and content rules.
What this workspace accepts and produces
Output
- JPEG, PNG, or WebP with actual format, dimensions, and bytes re-read
- Individual downloads or a ZIP containing verified target results
- Reached, closest, failed, or could-not-verify status for every item
- Choose output sizes
- Review each image before publishing. The ZIP includes only verified outputs; the manifest lists every attempted output.
Local processing boundary
Decoding, resizing, encoding, metadata removal, verification, and ZIP creation run in this tab. Files, file names, settings, outputs, and execution history are not sent to Toolars analytics or storage.
Visible test method
The release benchmark prepares five mixed images as WebP under 200 KiB with a 1600 px longest edge and supported metadata removed, while preserving exportable successes when one item is unsupported.
- Sniff the source bytes and decode the real dimensions.
- Process serially, then re-read output magic bytes, dimensions, size, and supported metadata.
- Put only verified target results in the batch ZIP; keep other outcomes available for review or retry.
Important limitations
- PNG size targets are not predictable through a quality slider; WebP or JPEG may be a better fit.
- A smaller dimension is never used unless you authorize dimension reduction.
- ICC color profiles are not treated as removable EXIF/XMP metadata in WebP verification.
- Browser memory and codec support vary by device; reduce the batch or dimensions if processing cannot start.
- Toolars suggestions, not platform requirements. White padding keeps the whole image and may enlarge it. Size targets are not guaranteed.
- Select one to three sizes. Up to 12 source images, 36 outputs, and 32 MiB of retained results.
Common failures and recovery
The target cannot be reached
Allow dimension reduction, choose WebP or JPEG, or keep the closest verified result.
A file is rejected or cannot be decoded
Remove that item, export the successful results, and retry with a supported JPEG, PNG, or WebP.
A browser download is blocked
Retry the individual file or ZIP and check the browser download permission for this site.
Image delivery FAQ
How do I resize a 600 × 400 image without cropping?
Choose a 600 × 400 JPEG, PNG, or WebP, select Fit within width and height, and set a 300 × 300 box. With additional dimension reduction off, the result is 300 × 200. Check the verified dimensions before downloading; a byte-size target can still be missed.
How do I make a square image without cutting off the edges?
For the same 600 × 400 image, select Pad to exact size, set 300 × 300, and choose PNG with transparent padding. The image occupies 300 × 200 inside a 300 × 300 output. Inspect the padding and dimensions. If a size target is missed, review the closest result or revise the format or target.
Are images uploaded to Toolars?
No. This workflow uses local browser APIs and does not upload the source or result files.
Is 200 KiB the same as 200 KB?
No. 200 KiB is 204800 bytes; decimal 200 KB is 200000 bytes. If a portal sets a strict 200 KB limit, choose 195 KiB (199680 bytes) or less. Check the actual output bytes; reaching the size target does not guarantee portal acceptance.
What does could not verify mean?
The output exists, but a requested property could not be proven by the available parser. It is not presented as fully verified.