Image Optimization Checker
Check whether an image is ready to publish. TryImager reads your file locally, scores it out of 100, and shows exactly which characteristic is holding the score down — file size, format, dimensions or compression.
Your image is processed locally in your browser. It is never uploaded to our servers. No fixed size limit — we adapt to what your device can handle. Very large files may take longer or show a warning.
No display width given, so dimension recommendations are estimates based on a typical 1920 px layout.
A quick pass/fail read on any image
Use this checker when you already have an image and simply want to know whether it is fit to publish. It answers one question: is this file the right format, the right size in bytes and the right size in pixels for the way it will be shown?
The output is a score out of 100 plus a per-category breakdown, so a low result always points at a specific cause rather than a vague verdict.
How to read the result
Each category is scored independently, which is what makes the total actionable.
- 90–100: nothing meaningful left to fix. Publish it.
- 75–89: usable, with one clear improvement available — often a format change.
- 55–74: the file is noticeably heavier than it needs to be for its display size.
- Below 55: expect a real load-time cost. Format, dimensions and compression usually all need attention.
Common failures the checker catches
A camera JPEG dropped straight into a page at 4000 px wide. A PNG export used for a photograph because the design tool defaulted to it. A screenshot saved at 3x device pixel ratio. A logo saved as PNG when its transparency could ride along in a much smaller WebP file. All four are invisible in a browser and obvious in the breakdown.
Frequently asked questions
What does the checker actually check?
It reads your file's size in bytes, decodes it to get real pixel dimensions, samples the alpha channel for transparency, derives bytes per pixel, and compares all of that with common web delivery practice. Every value shown under Detected information comes from your file; everything under Recommendations is our interpretation of it.
Do I need to know my display width?
No. Without it the checker assumes a typical layout width for the use case you pick and labels the dimension advice as an estimate. Entering the width you actually display makes that part exact.
Does the checker change my file?
Not unless you press Optimize Automatically. Checking is read-only, and nothing is uploaded either way.