Signature Resizer
Prepare a signature to exact pixels with undistorted padding, JPG or PNG and an optional verified maximum KB, locally.
Runs on your device Processed locally in your browser. Nothing is uploaded.
Reduce a photo below your maximum KB with actual byte checks and optional smaller dimensions. No uploads or oversized downloads.
This is real maximum-byte targeting, not a quality-slider estimate. The shared upload-preparation operation checks each encoded candidate's bytes, with at most four resolutions and 32 JPEG encodes (one encode per resolution for PNG). It samples the original image each time, never repeatedly compresses an already-lossy candidate. It does not assume that encoder size changes monotonically.
The search is bounded, not exhaustive or globally optimal. An already-small photo is re-encoded and may grow; a target may be impossible within the quality/dimension safeguards. PNG preserves alpha; JPEG flattens transparency to white. Metadata such as camera/location information is not preserved. There is no perceptual quality guarantee, minimum-byte padding, exact-byte target or automatic portal approval.
One image per run, up to 100 MiB and 120 megapixels decoded/output, with a 20000-pixel axis cap. Browser memory can still limit large files. Output sizes differ between browser encoders; verify the actual downloaded result.
Capability baselines: ResizePixel KB reducer, Simple Image Resizer KB workflow and RedKetchup image-resize help (inspected 18 October 2026). Engine contract and independent decoded-output tests: issues #185 and #188.
Enter that maximum and try JPG. The tool returns a file only when its actual encoded bytes meet the limit. Smaller dimensions may be needed, but require your explicit permission. Some images cannot reach a limit within the safeguards; the error is an honest failure, not a claimed successful download.
It first fits within your maximum width/height without stretching or upscaling. Additional reduction occurs only when you enable Allow smaller dimensions and quality alone cannot meet the limit. The result reports the actual dimensions; check them against your application's minimum as well as maximum.
No. Encoding and byte verification happen on your device, without an account, upload, analytics payload or network-based codec.