Drop a folder, or click to choose images

JPEG · PNG · WebP · AVIF · HEIC · SVG · GIF · JXL · TIFF

CtrlVPaste
Web OptimizedWEBP · max 1920px

Files never uploaded · 100% client-side · I cannot see your photos · Privacy policy

Output pre-selected: QOI — drop any supported image

Free convert-to-QOI studio — any input welcome

This Studio link pre-selects QOI so you can convert to QOI immediately. Convert to QOI for tooling — a simple lossless still for engines and pipelines, not for `<img>` tags or CMS uploads.

Bring JPEG, PNG, WebP, AVIF, HEIC, GIF, SVG, and more — input format is never blocked when you convert to QOI. Encoding uses QOI for fast lossless tooling.

Looking for a specific source format? Use deep links like PNG to QOI or HEIC to QOI for conversion-focused copy, or stay here when your batch is mixed and you still want to convert to QOI.

Typical convert to QOI result

A ceramic mug product PNG converting to QOI for a local engine.

Similar size, QOI decode path

Ceramic mug product photo on a white backdrop
Ceramic mug product photo on a white backdrop
PNG · 480 KBQOI · 510 KB

Before · PNG480 KBProduct texture

After · QOI510 KBLossless QOI

Illustrative convert to QOI. Tooling container, not a web compressor.

How to use this converter

  1. Step 1

    Stay on convert to QOI

    This page already set output to QOI. You can convert to QOI from JPEG, PNG, WebP, AVIF, HEIC, GIF, TIFF, BMP, SVG, and more in one queue.

  2. Step 2

    Drop a mixed batch

    Add files or a folder. When you convert to QOI, decode and encode stay in the browser — nothing is uploaded.

  3. Step 3

    Download QOI

    Scrub quality, optionally set a size budget (JPEG, WebP, AVIF, JXL, PNG palette search), then download one file or a ZIP after you convert to QOI.

convert to QOI at a glance

convert to QOI at a glance
TopicWhat you getNote
WebNoDo not convert to QOI for sites
Lossless pixelsYesFrom decoded bitmap
vs PNGSimilar size oftenDifferent decode story
Size budgetSkippedWhen you convert to QOI
AlphaYesSupported

Why convert to QOI

Convert to QOI from PNG when a game engine or internal tool wants Quite OK Image. Convert to QOI from JPEG stores decoded JPEG pixels losslessly (the QOI will usually be larger than the JPEG).

Convert to QOI is not TinyPNG. It is not a web performance trick. Size budget skips QOI.

Keep PNG/JPEG for humans. Convert to QOI for software that implements the codec.

Typical results when you convert to QOI

Typical results when you convert to QOI
SourceBeforeAfterNote
PNG UI80 KB PNG~90 KB QOIContainer swap
JPEG photo2 MB JPEG~9 MB QOILarger — expected
Need webAnyConvert to WebPNot QOI

How to convert to QOI in Asset Melt

Drop mixed inputs. QOI encodes quickly in a worker.

No JPEG-style quality slider — lossless from the working bitmap.

GIF first frame / TIFF first page / HEIC bounce still apply before you convert to QOI.

When you should convert to QOI

QOI-aware tools and texture pipelines.

When convert to PNG encode time is the bottleneck in your own software (QOI is simpler to decode).

Skip convert to QOI for websites, email, and app stores.

Quality when you convert to QOI

There is no quality trade-off. If the source was lossy, QOI stores those artifacts losslessly.

Resize to the texture size the engine wants before you convert to QOI.

Do not enable PNG Reduce palette expecting it to affect QOI output.

Keep a PNG sibling for preview in normal apps.

Privacy when you convert to QOI

When you convert to QOI, Image processing is 100% client-side in your browser with WebAssembly. Your photos are not uploaded, I cannot see or recover them, and sampled session replay is UI-only and does not include image pixels (media is blocked). The site still sends usage analytics and crash reports — details are on the privacy page.

Convert to QOI never uploads the bitmap. GIF still uses the first frame only. TIFF uses the first page only. HEIC decodes to pixels via libheif before you convert to QOI.

Related conversions

Frequently asked questions

Yes. Drop JPEG, PNG, WebP, AVIF, HEIC, GIF (first frame), TIFF (first page), BMP, SVG, JPEG XL, or QOI and Asset Melt will convert to QOI locally. Mixed batches are fine.

Yes. When you convert to QOI, decoding and encoding stay on your device. Image processing is 100% client-side in your browser with WebAssembly. Your photos are not uploaded, I cannot see or recover them, and sampled session replay is UI-only and does not include image pixels (media is blocked). The site still sends usage analytics and crash reports — details are on the privacy page.

Size-budget encoding targets lossy codecs (WebP, AVIF, JPEG, JXL). If you convert to QOI as QOI, use resize instead of a byte cap — QOI is a simple lossless codec, not a quality slider.

Yes. Process the queue, then export every QOI result as a ZIP. Optional ZIP every 25 files (Pipeline options) makes Download save numbered parts with progress on the button.

Output uses QOI for fast lossless tooling in a Web Worker — the same Squoosh-grade stack, with no upload.

Usually the opposite. Convert to QOI stores decoded pixels losslessly. Use convert to WebP for smaller photos.

Not with normal HTML images. Convert to QOI only for software that loads QOI.

No. Size budget skips QOI. Resize before you convert to QOI if the engine wants a smaller texture.