Dimensions before quality sliders
A four-thousand-pixel-wide screenshot displayed at four hundred pixels wide should be resized first. Our Image Compressor lets you balance quality and file size in the browser before hitching a twelve-megabyte PNG to a profile update.
Honestly, half our support tickets about “stuck upload” disappear when we cap longest edge to sixteen hundred pixels and switch to WebP where browsers allow it.
Progressive JPEG can improve perceived load on slow connections even when byte count is only slightly smaller than baseline.
Treat compression as part of the form UX: show file size after shrink, let users confirm, then upload—surprises after a long spinner feel like app bugs even when the server is fine.
Format choices that matter
Photos: JPEG or WebP with sensible quality. UI screenshots with text: PNG or lossless WebP—banding on small type ruins trust. Animations: do not crush GIFs into JPEG; pick the right tool, not the smallest extension.
The Image Resizer helps when you need exact output dimensions for Open Graph or Play Store graphics without opening a desktop editor.
Strip EXIF when privacy matters; keep orientation metadata only when you truly need it and forgot to rotate before upload.
Perceived performance
Show a lightweight placeholder, compress in the background, upload the smaller file. Progress bars on huge originals lie about time remaining. Mobile users on metered plans notice every megabyte.
We compress marketing hero assets too—not only user content. Lighthouse scores and bandwidth bills both improve when discipline is default, not a pre-launch panic.
Compare before and after at actual display size, not at 100% zoom on a 4K monitor that nobody uses on mobile.
Checklist before ship
Max upload size documented, client-side resize optional but recommended, server validates MIME, CDN serves modern formats. Test on a throttled connection, not fiber at the office.
Compression is not “making it ugly.” It is matching bytes to purpose. We built the tool to be fast enough that developers actually use it during QA, not only designers on launch week.
Document max dimensions in API docs so mobile clients know what the server will reject before users wait thirty seconds for nothing.
Batch uploads should compress sequentially on the client when possible—parallel giant files still choke memory on mid-range phones even if the server could theoretically accept them.
Hero images on landing pages deserve the same pass as user uploads—we have shaved seconds off LCP by compressing assets we thought were “already optimized.”