Initializing... drag & drop files here
Supports: XCF
.xcf GIMP project, or click "+ Add Files" to pick one or more from your device. Batch conversion is supported, so an entire folder of GIMP projects can be processed in one go.XCF ("eXperimental Computing Facility," named for GIMP's UC Berkeley origin) is GIMP's native working format. It stores layers, channels, paths, selections, masks, and guides — everything you need to keep editing — but very little outside GIMP can open it. JPEG (ISO/IEC 10918-1) is the opposite: a lossy, flattened, single-layer raster that every browser, OS, photo viewer, social platform, and CMS handles natively. Exporting XCF to JPEG is how a GIMP project becomes a sharable image.
.xcf uploads by MIME type. JPEG (and JPG) are accepted everywhere and render inline in the browser.| Property | XCF | JPEG |
|---|---|---|
| Standard | GIMP-internal (no ISO spec) | ISO/IEC 10918-1 (1992) |
| First released | 1997 (GIMP 1.0) | 1992 |
| Layers | Yes (unlimited, with groups since GIMP 2.10) | No (single flattened raster) |
| Transparency | Yes (full alpha + layer masks) | No (8-bit RGB or grayscale only) |
| Color depth | 8-, 16-, 32-bit per channel | 8-bit per channel |
| Compression | Lossless RLE, plus zlib/gzip/bzip2/xz since GIMP 2.10 | Lossy DCT-based |
| Typical file size (4000×3000, 10 layers) | 60–120 MB | 1–6 MB at 85% quality |
| Browser support | None natively | Universal (since Netscape 2, 1995) |
| Editable after save | Yes — layers, paths, selections preserved | No — single rasterized image |
| Best for | Active editing in GIMP | Sharing, web, print, archiving |
GIMP's official documentation notes that values above 95 are generally not useful (file size grows quickly with no visible gain) and that the default 85 "usually produces excellent results." xconvert's "Image Quality (%)" slider follows the same scale.
| Quality | Use case | Approx. size vs 100% | Notes |
|---|---|---|---|
| 60–70 | Email thumbnails, previews | ~15–25% | Visible artifacts on smooth gradients and skin tones |
| 75–80 | Social media, blog inline | ~25–35% | Good balance for most web use |
| 85 (default) | General web, GIMP default | ~35–45% | Recommended sweet spot — artifacts rarely visible |
| 90–92 | Photo prints, portfolios | ~50–65% | Near-original fidelity for trained eyes |
| 95+ | Master copies, archival | ~70–100% | Diminishing returns; >95 grows file size with little quality gain |
No. JPEG is a single-image, single-channel format with no concept of layers, masks, paths, or groups — it stores one flattened RGB or grayscale raster. The converter automatically flattens visible layers (respecting your visibility toggles and opacities) before encoding. To keep editability, also export to PNG, TIFF, or keep your XCF original — converting JPEG back to XCF later cannot recover the discarded layer data.
JPEG does not support an alpha channel. Any transparent pixels become solid — typically white in most converters, including this one. If preserving transparency matters (logos, UI mockups, cutout product photos), export to XCF to PNG or XCF to WebP instead. Both keep full alpha.
Yes. The two extensions identify the same ISO/IEC 10918-1 file format. The shorter .jpg was historically used because Windows 95 and DOS limited extensions to three characters. xconvert offers both XCF to JPG and XCF to JPEG — output bytes are identical; only the filename extension differs.
For most web and social use, 80–85% is the sweet spot — visually indistinguishable from the original on screen and significantly smaller. For portfolio prints or archival masters, 90–92%. Above 95% the file grows quickly with no perceptible improvement (this is what GIMP's own documentation says). Below 70%, blocky artifacts appear in flat color regions and skin tones.
XCF stores every layer, mask, channel, path, selection, and undo-history hint at full bit depth — even invisible ones. A 12-layer, 16-bit-per-channel project at 4000×3000 can easily exceed 100 MB. JPEG flattens to one 8-bit RGB layer and applies lossy DCT compression with chroma subsampling, so a 5–10× size reduction at 85% quality is normal and expected.
Yes. Drag a multi-select or an entire folder onto the page. Each XCF is converted with the same quality and resolution settings, then provided as individual JPEG downloads or a single ZIP. Quality and resolution choices apply to the whole batch — there's no per-file override in one pass.
Yes. The XCF format is backward-compatible by design — newer parsers read older files. Files saved by GIMP 2.0 through 2.10 (including 2.10's zlib/gzip/bzip2/xz compressed variants) all import correctly. Files from GIMP 1.x are also supported. Forward compatibility, however, has limits: a layer-group structure introduced in GIMP 2.7 can't be opened by GIMP 2.6 — but xconvert always uses a current parser, so this only affects users opening exports in old GIMP installs.
Yes. Under "Image resolution," choose "Resolution Percentage" to scale uniformly (e.g., 50% for a half-size copy), pick a "Preset Resolution" (4K, 1440p, 1080p, 720p, etc.), or enter custom "Width x Height" with aspect ratio locked. Resizing happens before JPEG encoding, so the final file is genuinely smaller — not just displayed at a smaller size.
Three levers, in order of impact: (1) drop "Image Quality (%)" to 75 — typically halves file size with minor artifacts, (2) reduce resolution if the destination doesn't need full size — a 2000×1500 JPEG at 85% beats a 4000×3000 JPEG at 60%, (3) for further reduction without re-encoding the source, run the result through Compress JPEG.
xconvert handles typical XCF projects up to several hundred MB without issue. Very large multi-layer projects (1 GB+) may run into browser memory limits depending on your device. If a huge XCF fails, try first flattening in GIMP (Image → Flatten Image, save a copy) or exporting from GIMP at lower bit depth before uploading.