Drop a folder, or click to choose images
JPEG · PNG · WebP · AVIF · HEIC · SVG · GIF · JXL · TIFF
Files never uploaded · 100% client-side · I cannot see your photos · Privacy policy
Pipeline ready: JPG → QOI (any input still accepted)
Asset Melt Studio is a JPG to QOI converter that runs entirely on your device. Fast lossless QOI for tooling pipelines — not a web format. QOI is simple and quick, which is the point.
Drop one JPG or a whole folder — the pipeline is already set to QOI using QOI for fast lossless tooling. That is the JPG to QOI workflow people search for: convert JPG to QOI without an upload, then resize, crop, or hit a size budget (when the codec allows) before you download.
Input is not locked to JPG: you can still open JPEG, PNG, WebP, AVIF, HEIC, GIF, and more in the same session. The JPG to QOI URL simply pre-selects QOI so jpg to qoi jobs start in one click.
A landscape JPEG converted to QOI for a local tooling pipeline.
Larger, faster to decode in QOI tools
Before · JPEG1.9 MB — Photo
After · QOI8.8 MB — Lossless pixels
Step 1
You are already on the JPG to QOI converter. Output is pre-selected as QOI. You can still drop mixed formats — the JPG to QOI URL is a starting point, not a file-type lock.
Step 2
Drag JPG images onto the studio, click to choose, or paste. Folder drops queue nested images. Then process — JPG to QOI encoding runs in Web Workers on this device.
Step 3
Use the before/after scrubber until the JPG to QOI result looks right. Adjust quality, crop, or resize, then download one QOI or a ZIP of the batch.
| Topic | JPG | QOI |
|---|---|---|
| Web | JPEG yes | QOI no |
| Lossless from pixels | No (JPEG) | Yes (from decoded JPEG) |
| Typical size | Smaller JPEG | Larger QOI |
| Size budget | Supported | Skipped |
| Audience | Everyone | Tooling |
JPG to QOI (JPEG to QOI) wraps decoded JPEG pixels in Quite OK Image. QOI is for tools, games, and pipelines that want lossless stills without PNG’s complexity.
The QOI will usually be larger than the JPEG. You are not compressing for the web; you are changing container for speed of decode in specific software.
Size budget skips QOI. Browsers will not display QOI in an `<img>` tag.
| Source | Before | After | Note |
|---|---|---|---|
| Phone JPEG | 2 MB JPEG | ~9 MB QOI | Expected |
| Resized texture | 2 MB JPEG | ~1.2 MB QOI | Resize first |
| Need web | 2 MB JPEG | Use WebP/AVIF | Not QOI |
Drop JPEG. QOI encode locally. Fast.
No quality slider in the JPEG sense — QOI is lossless from the decoded bitmap.
Download for your tool chain, not for Shopify.
A pipeline that already speaks QOI.
When PNG encode time is the bottleneck in a local tool (QOI is simpler).
Skip JPG to QOI for websites and email.
No extra quality to pick. If the JPEG was blocky, QOI stores that blockiness losslessly.
Resize before QOI if the tool wants small textures.
Do not expect CMS support.
Prefer PNG if humans need to open the file in Preview/Photoshop without plugins.
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. That includes every JPG to QOI job — the converter never needs your files on a server.
Upload compressors send your bitmap to someone else’s API. Asset Melt keeps jpg to qoi on this device. Session replay, if sampled, is UI-only and does not include image pixels.
Related conversions