Compress Image to 100KB
Use a 100KB target with real quality search, optional Strict resizing, and transparent Alpha-preserving output behavior.
Category: compression · Priority: P1
Static JPG/JPEG, PNG, and WebP. Animated WebP is rejected. Processing stays in this browser.
How to target 100KB
- Choose JPG, PNG, or static WebP.
- Review the target, search mode, output format, and JPG background if relevant.
- Inspect exact bytes, final quality, scale, and dimensions before downloading.
Room for more image detail
100KB often permits higher quality or larger dimensions than 20KB or 50KB, but results still depend on image complexity and format.
Strict and same-dimension choices
Strict may resize proportionally only when quality is insufficient. Keep dimensions prioritizes unchanged pixels and honest status.
Transparency-aware output
WebP and PNG preserve Alpha. Explicit JPG output composites transparent pixels over the chosen background.
Actual candidate sizes
Non-monotonic encoder results are handled by boundary refinement and real-candidate ranking within a hard attempt limit.
Browser-local workflow
No image, filename, target, or image-dimension analytics are sent to PicRecast.
100KB compression FAQ
Is 100KB exactly 100,000 bytes?
Yes. The target uses decimal KB and success requires an output no larger than 100,000 bytes.
What gets prioritized in Strict mode?
It first seeks a target-meeting result, then favors more pixels, higher quality, and closeness to the target.
Can I explicitly convert formats?
Yes. Format conversion is opt-in and is disclosed in the result.
Does the Worker use a server?
No. A Web Worker is a browser thread; the controlled fallback also remains local.
Nearby size targets
Compare 50KB, 200KB, or enter a custom target.