Convert stills, video, and audio in the browser. Pair pages and format hubs list every conversion this site actually runs. Nothing is uploaded.
Runs in your browser · Nothing uploaded
Every conversion pair is its own page. Start from the format you have, or the format you need.
A short list. Every other pair is on the hubs above. The convert grid doesn't dump a hundred cards.
Format conversion is the job most “free” sites use as bait for an upload. A photo off an iPhone, a PNG that a form won't accept, a clip that needs WebM, none of that requires a server. This category is the converters I actually use: decode on this device, re-encode on this device, download from this device.
Each pair is its own URL so a search for “WAV to MP3” can land on a page that only does that job. Format hubs under /formats/ list every conversion into a container and out of it that I'll stand behind. If a pair is missing, the encoder isn't here, not because it's paid.
Hand-built stills (HEIC, PNG, JPEG, WebP, AVIF, Base64, PDF) sit in the grid. Video and audio generic pickers stay at /video/convert and /audio/convert. Batch convert is for a folder of stills.
HEIC to JPG is the iPhone off-ramp. Phones save HEIC because it's smaller; Windows, printers, and a lot of upload forms still want JPEG. The decoder runs in the tab, so the original, GPS and all, isn't posted anywhere. Quality is yours to set; around 90 is close to what you already had.
PNG to JPG is for photographs that were saved losslessly and are now too big. JPEG will usually cut the size hard. It will also flatten transparency and smear hard edges, so logos and UI screenshots should stay PNG or go to WebP instead.
JPG to PNG doesn't restore detail JPEG already threw away. It stores the current pixels losslessly, which is useful when a tool chain insists on PNG or you need a format that will survive another edit without a third generation of JPEG artefacts.
PNG to WebP is the usual way to ship a graphic on a website without the PNG weight. WebP can keep transparency. Lossy WebP is for photos; if the source is flat colour and type, you still want to look at the result before you commit.
JPG to WebP re-encodes an existing JPEG into a format most browsers prefer for photos. You won't get a miracle: the JPEG damage is already in the pixels. You may get a smaller file at a similar viewing size.
WebP to PNG decodes a WebP back to a lossless PNG. Use it when an editor or a printer won't open WebP, or when you want a copy you can keep editing without another lossy pass.
Convert to AVIF encodes PNG or JPEG as AVIF, which is often smaller than WebP at the same visual quality. Support is broad now, but not universal. If a recipient is on an old browser or a picky CMS, JPEG or WebP is the less annoying answer.
Image to Base64 turns a file into a data URL or raw base64 string. That's for embedding a small icon in CSS or JSON, not for emailing a 12-megapixel photo as text. The output is larger than the file; that's how base64 works.
Base64 to Image is the reverse: paste a data URL or a raw string and download the image. It is handy when a log, an email, or a CMS field contains the bytes and you just want the picture back.
Image to PDF wraps one or more images in a simple PDF. It isn't a layout program. Pages follow the image sizes; there's no letterhead editor. For a stack of scans that need to be one attachment, that's enough.
HEIC to JPG if the destination wants JPEG (most forms, Windows, print kiosks). If you need transparency later, that's the wrong destination, but iPhone stills are photographs, so JPEG is usually correct. Batch convert if you have a whole roll.
Logos, diagrams, screenshots of text, and anything with a transparent background. JPEG has no alpha channel and it puts ringing artefacts on sharp edges. Keep PNG, or use WebP if you need both size and transparency.
Yes. These pages never upload. For many files at once, use batch convert in the Batch category, same in-browser encoders, results in a zip. The single-file pages exist so you can see one result before you commit.
There is no server to upload to. Each page is a static file, and the work happens in your browser. Your file is read from disk into memory, processed, and handed back as a download. Once the page has loaded you can disconnect from the network and it keeps working. The longer explanation
