Testing methodology

ImgCase combines automated Chrome tests with targeted manual inspection. Passing tests means the checked workflow behaved as expected; it does not mean every possible image or browser is guaranteed to work.

Automated checks

• Every published tool loads a sample, exercises controls, and produces a non-empty download.
• Text files, empty images, truncated JPEGs, invalid PDFs, and multi-file workflows have recovery checks.
• Desktop and mobile layouts are checked for overflow, keyboard focus, menus, and download placement.
• Canonical URLs, Open Graph URLs, robots.txt, sitemap.xml, structured data, and domain redirects are tested.

Manual checks

We inspect output quality, small-screen layout, browser download behavior, metadata claims, and whether visible copy matches the implemented capability.

Known limits

Processing depends on browser memory, canvas size limits, file complexity, and device performance. Very large images, unusual color spaces, encrypted documents, and malformed containers can fail even when their extension is supported.

Report a reproducible problem through the contact page.