Extract images from ORA, on your device. Nothing ever uploads.

Drop up to 20 ORA files below — get the flattened canvas, the thumbnail and every layer PNG out byte-for-byte, exactly as stored. Download each image, or all of them as a ZIP.

Your file data never leaves the device
ORA from GIMP, Krita, MyPaint, layer order
Batch up to 20 files + ZIP
Original filenames, sequential ZIP names

Add your ORA files

Drag & drop ORA files here

or browse your files · you can also paste from clipboard (Ctrl+V)

An ORA is a ZIP package of OpenRaster XML and layer PNGs — read on this device with JSZip, images returned in layer order from stack.xml, and mimetype, stack.xml, __MACOSX and hidden entries skipped. Every image downloads byte-for-byte, exactly as stored — no re-encoding, no quality loss. Layer PNGs are full-canvas images per the OpenRaster spec. EMF, WMF, HEIC and TIFF images cannot be previewed in most browsers, so they show a “preview unavailable” note — they still download byte-for-byte. SVG images are extracted as-is; their preview may not render in some browsers. PSD, XCF, DOCX/XLSX/PPTX and KRA files, PDFs and CBZ/CBR archives are refused with a pointer at the right tool or fix; an Oracle database .ora config file is refused with an explanation.

No files yet. Everything stays on this device. Downloads start instantly.

About this extractor

One ZIP per file, plus a combined ZIP. Each ORA becomes its own ZIP of images with sequential names (image-01.png, image-02.png, …) in layer order; “Download all as ZIP” bundles every file into its own folder.
ORA from GIMP, Krita, MyPaint and Paint.NET. OpenRaster is the open layered-image format those programs share — one file several programs can read. stack.xml lists the layers in order with each layer's stored PNG under data/. No upload, no desktop tool, no 10 MB cap.
Merged image first. mergedimage.png is the flattened render of the whole canvas that the program saves inside every .ora at save time — the picture as you see it on the canvas, all layers merged. It is the first image this page hands you, labelled “Merged image — flattened canvas”.
Thumbnail second. thumbnail.png is the small preview the program stores for file managers. It comes out right after the merged image, labelled “Thumbnail — small preview”.
Layer order, not stored order. Layer images come out in the order stack.xml lists them — the same order as the layer stack — not the order the package happens to store them. Each layer is labelled with its name and group path, for example “Background / Sky”. Image entries nothing references come last, labelled Unreferenced, and you can reorder images on each file card.
Layer PNGs are full-canvas. Per the OpenRaster spec, each layer PNG covers the whole canvas — so a small brush stroke still downloads as a full-size PNG. The spec mandates PNG for layer files, and this page extracts whatever image bytes a layer actually holds.
Byte-for-byte for every format. PNG, JPEG, GIF, SVG, WebP, BMP, TIFF, EMF, WMF, AVIF and HEIC all download exactly as stored — no re-encoding, no rasterization, no quality loss.
Original filenames on per-image downloads. Download one image and it keeps the filename from inside the file — mergedimage.png, thumbnail.png, or the layer's stored name (data/layer1.png downloads as layer1.png); ZIP downloads use sequential names so the images always open in layer order.
EMF, WMF, HEIC and TIFF previews. Most browsers cannot display EMF, WMF, HEIC or TIFF, so those images show a “preview unavailable in this browser — download to view” note instead of a broken image. They still download byte-for-byte.
SVG images are extracted as-is. An SVG downloads exactly as stored; most browsers preview it, but one that references external files or fonts may not render in a preview — the file itself is unaffected.
Animated GIFs keep their animation. Nothing is rasterized, so an animated GIF downloads with all its frames — unlike a converter, which keeps only the first frame.
Metadata stays in the files. Extraction is verbatim, so EXIF and other metadata inside each image is kept — including location data, if the image has any. Strip it yourself before sharing an image publicly.
No text extraction. This tool pulls out images only — it does not extract the document's text. The words stay in the file.
Missing stack.xml falls back to archive order. If stack.xml is missing but the mimetype is right and data/*.png entries exist, the images still extract in stored order, with a warning on the card — they still come out byte-for-byte.
Layer paths must stay inside the file. A stack.xml layer src that escapes the archive (for example “../external.png”) is refused — layer paths are relative and contained, by the spec.
Unmapped layer files fall to the unreferenced tail. If stack.xml names a layer file the package does not hold, or lists no layers at all, the images are listed in stored order with a warning on the card — they still extract byte-for-byte.
A 25 MB safety cap applies per file, and 20 files per batch. Reading very large files in the browser is memory-heavy. Most ORA files are well under 25 MB, far below the cap. There is no daily limit and no account.

Have a Krita document instead? Extract Images from KRA reads KRA files the same way. Have a Word document? Extract Images from DOCX reads DOCX files the same way. Have a spreadsheet? Extract Images from XLSX pulls its images out. Have a PDF? Extract Images from PDF pulls its images out.

Privacy you can verify, not just trust

Most online ORA tools upload your files to their servers first — and some keep a download link live for 30 days, or cap free conversions at a few per month. This one can't: each image is pulled out of your file bytes entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no file fetched after load for the extraction itself. Don't take our word for it:

New cross-origin requests during use: 0

Press F12 to open developer tools, then the Network tab.
Extract any file above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
Extra credit: disconnect your internet after this page loads — extraction still works.

How to extract images from an ORA without uploading it

Every "free" online ORA tool you've used uploads your file to a company server, extracts it there, and — in several documented cases — keeps a copy or a live download link for days, or limits free users to a few conversions a month. For artwork you drew, were sent in confidence, or simply wouldn't post publicly, that's an unnecessary risk. The safer approach is to extract the file where it already is: on your own device.

This tool does exactly that. When you drop an ORA here, your browser:

Checks the file is really an ORA file — by its magic bytes, not its name — so a JPEG renamed .ora is refused with a clear message, a PSD renamed .ora is refused with a note to open it in GIMP or Krita and save it as .ora, a CBZ or plain .zip renamed .ora is refused with a pointer at the CBZ tools, a PDF renamed .ora is refused with a pointer at the Extract Images from PDF tool, a DOCX renamed .ora is refused with a pointer at the Extract Images from DOCX tool, an XLSX renamed .ora is refused with a pointer at the Extract Images from XLSX tool, a PPTX renamed .ora is refused with a note that it is a presentation, a Krita .kra file is refused with a pointer at the Extract Images from KRA tool, an Oracle database .ora config file is refused with an explanation that it is text, not an image, and a password-protected archive is refused with an explanation instead of a cryptic error. A real ORA saved with the wrong extension still extracts.
Reads the file's own structure and pulls the images in layer order — stack.xml lists the layers in the same order as the layer stack, each with its stored PNG under data/, so the merged image comes first, then the thumbnail, then the layer PNGs in layer order, each labelled with its name and group path. mimetype, stack.xml and macOS entries are skipped, and everything skipped is listed on the file card.
Hands you the originals — download one image and it keeps its original filename (a layer stored as data/layer1.png downloads as layer1.png); download the file as a ZIP and every image is renamed image-01, image-02 and so on in layer order. Nothing is re-encoded, rasterized or resized at any point: the bytes you download are the bytes that were stored in the file.

What makes this extractor different

Most pages that top the results for this search convert on a server, or handle one file at a time with no previews — instead of handing you the images themselves. The desktop options are installs, not browser tools. This page does the simpler job, and does it fully in the browser: no upload, no monthly cap, no account, no 10 MB limit, a batch of 20 files, layer order with group-path labels and unreferenced images labelled, original filenames on per-image downloads, sequential names in the ZIP, and a live network-request counter so you can verify the privacy claim yourself.

Honest limitations

Verbatim means verbatim — no quality recovery

JPEG throws away detail when it compresses, and extracting cannot put it back. But nothing is lost either: the source bytes download unchanged, in every format. There is no quality setting because there is nothing to re-encode.

Layer PNGs are full-canvas images

Per the OpenRaster spec, each layer PNG covers the whole canvas — so a small brush stroke still downloads as a full-size PNG. That is how the format stores layers, not a choice this page makes; the merged image is the compact way to share the finished picture.

Metadata stays in the files

Extraction copies the stored bytes, so EXIF and other metadata inside each image is kept — including location data, if the image has any. The file's own package parts are skipped, and listed on the card, but the images themselves are untouched. Strip metadata yourself before sharing an image publicly.

The merged image is a snapshot at save time

mergedimage.png is the flattened render saved when the file was last saved — not a live re-render. If the file was edited after its last save without saving, the merged image shows the older state.

No editable layer stack, no text

Extraction cannot restore the editable layer stack — only GIMP, Krita or MyPaint reassembles that. This tool pulls out images only: it does not extract the document's text.

Layer order, when the file cooperates

Layer order comes from stack.xml and each layer's stored PNG. If a file's stack.xml is missing, the images fall to stored order with a warning on the card — they still come out byte-for-byte. Unreferenced images are listed last as Unreferenced. A layer path that escapes the file is refused outright.

Frequently asked questions

Do my files upload anywhere?

No. Your ORA files are extracted entirely in your browser — your file data never leaves the device, and the only third-party requests are the site's own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the extractor.

What is an ORA file, and how is it different from KRA?

An ORA file is an OpenRaster document — the open layered-image format that GIMP, Krita, MyPaint and Paint.NET (with a plugin) can all write — holding the layer stack, a flattened render and a thumbnail in a ZIP package. A KRA file is Krita's own layered format, with the same idea but a different layout (maindoc.xml instead of stack.xml, paint layers stored as binary tile data). This page reads ORA files; for a KRA file, use the Extract Images from KRA tool.

What is stack.xml?

stack.xml is the file inside every ORA that describes the document: the canvas size and the layer tree, with each layer's stored PNG, its name, opacity and blend mode, grouped in nested stack elements. This page reads stack.xml to hand you the layer PNGs in layer order, with each layer labelled by its name and group path — for example “Background / Sky”.

What about password-protected ORA files?

OpenRaster itself has no password protection, so a protected archive is not a plain .ora file — this page refuses it with a clear message instead of asking for a password. Open it with the password in the program that made it and save an unprotected copy, then extract that.

Merged image vs individual layers — what is the difference?

mergedimage.png is the flattened render of the whole canvas saved inside the file — every layer merged into one picture. The layer PNGs are the individual layers, one full-canvas PNG per layer, in stack order. This page hands you the merged image first, then the thumbnail, then each layer PNG, so you can reuse the finished picture or rebuild the stack yourself.

Are the images re-encoded, or do I get the originals?

You get the originals. Every image downloads byte-for-byte exactly as stored in the file — no re-encoding, no rasterization, no quality setting, no quality loss. Per-image downloads keep the original filename (data/layer1.png downloads as layer1.png); ZIP downloads use sequential names (image-01.png, image-02.png, …) in layer order.

Does extraction keep metadata like EXIF location data?

Yes. Extraction is verbatim, so EXIF and other metadata inside each image is kept — including location data, if the image has any. The file's own package parts are skipped and listed on the card, but the images themselves are untouched. Strip metadata yourself before sharing an image publicly.

What should I do with a DOCX, XLSX or PPTX file?

A DOCX is a Word document, an XLSX is an Excel workbook and a PPTX is a PowerPoint presentation — all three are ZIP archives like an ORA, but with a different layout, so this page refuses them. For a DOCX, use the Extract Images from DOCX tool, which reads Word documents the same way this page reads OpenRaster files. For an XLSX, use the Extract Images from XLSX tool. A PPTX is a presentation, not a layered image — open it in PowerPoint and export its pictures from there.

Which programs open ORA files?

GIMP, Krita and MyPaint all open ORA files natively, and Paint.NET opens them with a plugin — that is the point of the format: one layered file that several programs can read. Only those programs can restore the editable layer stack, though: this page pulls the images out, but it cannot rebuild the stack for you — open the file in GIMP, Krita or MyPaint to edit the layers.