Compress an image to 30KB.
Use this 30KB preset for small profile uploads, lightweight thumbnails, and document portals that allow a little more detail than 20KB.
Local processing. Measurement, resizing, encoding, and ZIP creation happen in this tab; selected images are not sent to imgrove. Privacy details
Result will appear here
How to use Compress Image to 30KB
- Trim a scanned signature or document mark to a narrow rectangle while leaving a small safe margin around the ink.
- Upload it with the 30KB, JPG, Auto, 1000px, and EXIF-removal defaults; do not stretch the strip into a square.
- Inspect the after dimensions and zoom the preview to confirm thin strokes remain continuous and the background stays clean.
- If the 30KB pass creates halos, try a cleaner grayscale source or WebP when accepted; if PNG fails, return to JPG after trimming more whitespace.
How it works
- Auto mode evaluates JPEG quality at the 1000px cap and reduces the wide signature-strip dimensions only when quality search cannot meet 30KB.
- The byte check is applied to the downloaded blob, so the target includes encoder overhead and any EXIF the user explicitly asks to preserve.
Formats and limits
| Input | A cropped signature, initials, stamp, or small thumbnail in JPG, PNG, or WebP. |
|---|---|
| Default output | JPG, Auto target, 1000px maximum side, 80% manual fallback. |
| Byte rule | At or below 30,720 bytes with a visible target-met state. |
| Aspect ratio | Preserved; a 1200x400 strip remains horizontal rather than being stretched to a square. |
| Metadata | Removed by default; signature scans rarely benefit from camera EXIF. |
| Edge tradeoff | PNG keeps hard edges but may miss 30KB; JPG or accepted WebP is usually more predictable. |
Real failure cases
- Large blank margins consume working pixels and can force the actual ink into too few pixels; trim the scan before compression.
- Repeated JPG passes amplify ringing around thin strokes; return to the original scan instead of compressing the previous download again.
- If the receiving form stretches or clips the signature, fix its required pixel ratio first because a 30KB success does not change layout rules.
Example result to verify
| Reference input | 1200x400 synthetic signature-strip PNG with dark thin strokes on a light background. |
|---|---|
| Preset | 30KB, JPG, Auto, 1000px cap, EXIF removed; manual fallback starts at 80%. |
| Tested result | Downloadable image/jpeg blob at or below 30,720 bytes with target met and output dimensions reported. |
| Human check | The thinnest strokes should remain continuous without a wide halo; otherwise trim margins or change an accepted format. |
Best for
- Scanned signatures, initials, and narrow document marks that need a little more edge detail than 20KB allows.
- Small profile thumbnails for portals with a hard 30KB ceiling.
- Checking whether whitespace, not image content, is wasting the available byte and pixel budget.
What you get
- A JPG capped at 30,720 bytes when the encoded signature or thumbnail can fit.
- A 1000px maximum side, Auto target search, 80% manual fallback, and metadata removal as distinct defaults.
- Visible before/after dimensions and bytes so a wide signature strip can be checked independently of a portrait workflow.
Before you download
- A scan with large white margins may become needlessly small because those margins still count toward the working dimensions.
- Thin pen strokes can show JPG ringing; WebP is worth testing only when the receiving form accepts it.
- 30KB does not imply a particular aspect ratio, so preserve the signature strip ratio unless the form publishes exact pixels.
30KB workflow for signatures and narrow document marks
The extra 10KB over a 20KB target is most useful when it protects fine edges, not when it encodes empty margins. This preset therefore pairs a 30KB cap with a wider 1000px working edge and an 80% manual fallback for signature-like sources.
- Default configuration. 30KB target, JPG output, Auto search, 1000px maximum side, 80% manual fallback, and EXIF removal. The wider cap accommodates a horizontal signature strip without forcing a square crop.
- Real task. Use it for a scanned signature, initials, stamp preview, or small profile thumbnail when the upload rule states 30KB or less.
- Browser regression sample. The test suite loads a 1200x400 synthetic signature-strip PNG and requires a downloadable JPG no larger than 30,720 bytes with target met, output dimensions reported, and metadata removed.
- 30KB-specific recovery. Trim white borders before lowering quality. If dark strokes show a bright halo, use a cleaner monochrome source, test WebP when supported, or keep JPG and reduce the working width instead of repeatedly recompressing an already damaged file.
- Verification. Zoom the result and trace the thinnest stroke from end to end. Also confirm the form wants a maximum file size rather than an exact-size or exact-dimension signature.
Next steps
- Resize Image by Dimensions - set a required signature width and height without changing its ratio accidentally.
- Black and White - prepare a simpler high-contrast source when color noise wastes bytes.
- Image Size Checker - confirm the signature bytes, pixels, format, and metadata after download.
- Compress Image to 50KB - keep more edge detail when the destination accepts a 50KB file.
Questions about Compress Image to 30KB
Why trim white space before compressing a signature to 30KB?
The compressor preserves the whole canvas ratio. Wide blank margins make the ink occupy fewer output pixels, so trimming them protects stroke detail without spending more bytes.
Is PNG always better for a scanned signature?
PNG often keeps hard edges cleaner, but browser PNG encoding may remain above 30KB. Use it only when the result fits and the portal accepts PNG.
Can I make a 30KB signature an exact pixel size too?
Yes, but set the required width and height with the resizer first. Then compress that result to 30KB and verify both rules separately.
Why should I avoid compressing the downloaded JPG again?
A second lossy pass can add halos and break thin strokes. Re-run the original scan with a tighter crop or different format instead.