Local image data
The free browser tool processes one selected image in the browser. File names, pixels and generated output are not sent to a product API or analytics.
Resize
Browser-side toolResize an image to exact or proportional dimensions without uploading it to a server.
Image tools
Choose an image task, drop one local file, tune format or quality and compare the output before downloading.
Image Resizer
Set width, height or both. PixelBatch preserves aspect ratio when one dimension is blank.
Preview and output
Choose one image to see source preview, output metrics and download controls.
Folders, queues, saved presets and automation need account controls, upload validation and retention rules.
Support
Use the result first. Support and promotional areas stay separate from the useful result.
The free browser tool processes one selected image in the browser. File names, pixels and generated output are not sent to a product API or analytics.
Browser-side processing validates limits and creates a transform plan; Canvas re-encodes the image to resize, crop, convert or strip metadata when supported.
Batch folders, larger files, saved presets, integrations, API, high-resolution automation and AI credits remain account features.
No. PixelBatch uses browser memory and object URLs only; it does not use localStorage, sessionStorage or a product upload endpoint.
Not in the free browser tool. Batch processing, folders and larger files need account controls for quota and retention.
Background cleanup, large conversion queues and API integrations require explicit data and safety controls. The free tool remains a local one-image task.
Subject masking or background removal would require AI or segmentation infrastructure, so the public tool does not send pixels out of the browser.
Bulk folders and high-resolution queues need account upload controls for a paid task.
Automation is useful for teams, but it changes the data boundary from browser-only to account-backed jobs.