Convert

Format conversion looks like one job but is really a family of them, each with a distinct failure mode. PNG to JPG has to decide what happens to transparency. JPG to PNG has to explain why the file got bigger and the quality did not improve. HEIC to JPG needs a decoder most browsers do not carry. AVIF conversion needs to detect the browsers that silently write PNGs while claiming AVIF. That is why every direction here is its own page with its own warnings — the engine is shared, the honesty is specific.

The iPhone corridor is the busiest: HEIC photos open fine on Apple hardware and almost nowhere else, so the HEIC converter loads a WebAssembly decoder on demand and turns them into universally-readable JPEGs at your chosen quality — on your device, which matters, because camera rolls are exactly the images people should not be uploading to converter sites.

The document corridor runs both ways: images become a paginated PDF through a writer that builds the PDF structure directly in your browser, and PDFs become JPG or PNG pages rendered at screen, web or print resolution. Between the corridors sit the web-performance conversions — WebP and AVIF in and out — and the developer utilities, SVG rasterisation at exact pixel sizes and Base64 for the rare inlining case that genuinely helps.