OpenImages is an independent project run by one developer. This page describes how the tools and content actually get built — what runs in your browser, how each tool is verified, and what the site does and doesn't do.

What runs in your browser

Every tool on this site processes images entirely in your browser. Files you load are read by FileReader into browser memory and rendered to a <canvas> via the Canvas 2D API. Resize uses a Lanczos filter implemented in JavaScript; format conversion (PNG/JPEG/WebP) uses the browser's built-in canvas.toBlob(); SVG vectorization uses an in-browser tracer. No file is POSTed to a server, and no image data leaves the browser tab during the tool path.

Ads come from Google AdSense (publisher ID ca-pub-8761907366448308). AdSense uses cookies and shares limited data with Google's ad network when you consent. The cookie banner is a real consent gate: AdSense scripts do not load until you accept. If you decline, no ad cookies are set. Ad slots are clearly marked Sponsored.

How tool reliability is verified

Every tool is covered by an automated end-to-end test that runs on every deploy. The "Last verified — N tools passing" line in the footer is set by CI: it reflects the date of the last green run and the count of tools that passed. If a test breaks, the footer reflects that on the next build, and the broken tool is fixed before the line goes back to all-passing.

How content is written

Tool behavior is implemented and verified by hand against the source specifications: ISO/IEC 10918 for JPEG, the W3C PNG spec, the WebP container spec, the SVG 1.1 / 2 W3C recommendations, and Caniuse for browser-support claims. Compression-vs-quality trade-offs and the limitations of in-browser encoders (no AVIF encoder in older Safari, for example) are documented per tool when relevant.

Long-form guides under /docs/ are drafted with AI assistance and lightly reviewed before publishing. The technical facts in those guides — what a spec says, what a codec does — are independently verifiable.

Comparison pages ("X vs Y") were previously published with light review. Those pages have been removed because the project couldn't maintain the factual bar they required without becoming an image-tool-review site, which isn't what OpenImages is. If a comparison page redirected you here, please use the actual products to compare them.

What the site doesn't do

• Paid placements, sponsored editorial, or guest posts. AdSense ads are clearly marked Sponsored and separate from editorial.
• Paraphrase competitor blog posts.
• Upload your images. Files stay in browser memory and are discarded on page close; nothing is sent to a server during the tool path.

How content stays current

When a codec gains or loses browser support, when a spec is revised, or when a new format becomes broadly usable, the affected page is updated. The CI test suite catches behavioral regressions on every deploy, and visible errors are fixed on the next deploy.

Reporting errors

If you spot a factual error, a broken tool, or content that's outdated, email support@openimages.app. The operator typically replies within 24 hours on weekdays. Substantive corrections are published with a Corrected YYYY-MM-DD note next to the affected paragraph.

Funding and monetization

OpenImages accepts no payment for tool listings, no affiliate revenue, and no sponsored editorial content. Monetization is via Google AdSense display ads (where approved) and occasional Buy Me a Coffee tips. Ad slots are clearly marked Sponsored and separate from the rest of the page.