XCF to JPS Converter
FileFlip converts XCF to JPS entirely inside your browser, using ImageMagick compiled to WebAssembly. The file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. That means no file-size limit, no queue and no account.
How do I convert an XCF file to JPS?#
- Drop your XCF file onto the converter at the top of this page, or click it to pick one from your computer. You can add as many as you like.
- Leave the target set to JPS and the conversion starts on its own. FileFlip downloads 14.1 MB of WebAssembly the first time and nothing after that, then runs ImageMagick on your own machine.
- Save the JPS file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting XCF to JPS lose quality?#
Yes, once. XCF keeps everything and JPS does not, so this is the first time the file meets a lossy encoder. At high quality the difference is hard to see, and it is worth keeping the XCF original, because every later re-save of the JPS loses a little more.
Is it safe to convert XCF files online?#
Yes, because nothing is uploaded. FileFlip converts XCF files inside the browser tab you already have open, using WebAssembly builds of the same engines a desktop converter would install. Your file is read from your own disk into the page's memory, and no request carrying it is ever made.
You do not have to take that on trust. Open your browser's network panel, run a conversion, and you will see the engine come down and your file go nowhere. There is no upload, no server-side copy, no retention window, and no account tied to what you converted.
How FileFlip works lists every engine, its version and its download size, and shows how to check for yourself that nothing leaves your machine.
What XCF to JPS actually does to the file#
Converting XCF to JPS runs on ImageMagick, downloads 14.1 MB of WebAssembly the first time and nothing after that, encodes a lossless source with a lossy encoder for the first time, and drops transparency, layers and extra images.
| Engine | ImageMagick |
|---|---|
| Conversion path | One step: XCF → JPS |
| Downloaded to your browser | 14.1 MB, once, then cached by your browser |
| Quality | Lossy, first generation |
| You get back | One file |
| Where it runs | In a background worker, so the page stays responsive |
What survives the conversion
| What is in the file | This conversion | Why |
|---|---|---|
| Transparency | Dropped | The target format has nowhere to put it. |
| Layers | Dropped | The target format has nowhere to put it. |
| Extra images | Dropped | The target format has nowhere to put it. |
Worth knowing before you start:
- ImageMagick is asked for a single image, so only the first frame, page, or icon size is read
What is an XCF file?#
An XCF file is the working document format GIMP saves to, keeping an image's layers, layer masks, channels and paths independently editable instead of merging them into one picture.
Keep a project as XCF while it's still being edited in GIMP, so layers, masks and paths stay available for later changes.
Convert XCF to PNG or JPEG once the image is finished and needs to be viewed or shared outside GIMP, since almost nothing else reads the layered file.
What is a JPS file?#
A JPS file is an ordinary JPEG photograph that holds two views of the same scene side by side, one for each eye, flagged as a stereo pair by an APP3 marker that most software simply ignores.
Save a stereo pair as JPS when the destination software, such as StereoPhoto Maker or an anaglyph viewer, reads the APP3 stereo marker and the pair needs to travel as one file.
Convert JPS to a plain JPG when only the flat side-by-side image matters, or split it into two separate JPGs when software needs the left and right views on their own.
XCF to JPS questions people ask#
Can Photoshop open XCF files?
No, Photoshop doesn't support XCF natively. GIMP itself is the only editor with full-fidelity support, though the browser-based Photopea can open XCF files with much of their layer structure intact.
What happens to my layers when I export XCF to PNG or JPEG?
Exporting an XCF file to PNG or JPEG merges every layer into one flat image, bakes layer masks and channels permanently into the pixels, and rasterizes any text so it can no longer be edited. Paths and guides are dropped entirely, since neither format has anywhere to store them.
Why won't GIMP open my old XCF file, or an old GIMP open a new one?
XCF's structure has changed across GIMP versions: layer groups, added in GIMP 2.7, won't open in GIMP 2.6 or earlier, and a text layer created in modern GIMP degrades to a flat rasterized layer if opened in GIMP 1.2. Saving from a newer GIMP generally isn't safe to assume an older GIMP can read.
What's the difference between XCF and OpenRaster?
XCF is GIMP's own internal working format, built to mirror GIMP's internal engine and prone to changing between versions, while OpenRaster (.ora) is a format GIMP helped develop jointly with Krita specifically for interchange between different programs. GIMP's own documentation recommends OpenRaster over XCF when a layered file needs to move between tools or be archived long-term.