GIMP GEGL Filter Layers: Non-Destructive Editing That Survives a Reopen

The Problem: Baked Pixels Kill Iteration

Apply a Gaussian blur in most editors, save, close, and reopen — the blur is permanent. You cannot dial the radius down, mask it, or tweak it without redoing the whole stack. GIMP 2.10+ solves this by storing the operation, not the result, in a filter layer. The pixels stay untouched until you export.

How GEGL Filter Layers Work

GIMP's core engine, GEGL (Generic Graphics Library), represents each filter as a node in a directed acyclic graph. A filter layer is simply a serialized GEGL operation — gegl:gaussian-blur, gegl:curves, gegl:color-balance — with its parameters (radius, curve points, strength) saved as metadata in the XCF file. When you move a slider, GIMP re‑evaluates the graph from that node forward, rendering only the affected tiles. This design enables:

• Multi‑threaded tile rendering across CPU cores
• Optional OpenCL GPU acceleration (toggle in Edit > Preferences > System Resources)
• Consistent behavior whether driven from the UI, a Python‑Fu script, or a batch CLI

Creating and Managing Filter Layers

Two entry points exist:

1. Layer > New Filter Layer — pick a category (Blur, Colors, Enhance, Noise, etc.) and a specific filter. The new layer appears in the Layers dialog with a filter icon (⚙).
2. Right‑click an existing layer > Convert to Filter Layer — wraps the layer's content in a filter group; useful when you've already painted a mask and want to add live adjustments on top.

Filter layers behave like regular layers: toggle visibility, reorder, add layer masks, change blend mode (Normal, Multiply, Overlay…), and group them. The Layers dialog shows the active filter name and a disclosure triangle for its parameters.

Worked Example: Iterative Color Grading Without Commitment

Scenario: you are balancing a 16‑bit floating‑point landscape (4000×3000) and want to push shadows, protect highlights, and add a subtle split‑tone — all reversible.

1. Set precision: Image > Precision > 16-bit floating point. This prevents clamping when curves push values beyond 0–1.
2. Add a Curves filter layer: Layer > New Filter Layer > Colors > Curves. Pull the lower‑left anchor up to lift shadows; add a control point at 25% and drag down slightly to compress midtones.
3. Add a Color Balance filter layer: Layer > New Filter Layer > Colors > Color Balance. Target Shadows, shift toward cyan/blue; target Highlights, shift toward yellow/red. Because it's a separate layer, you can mask the effect to only the sky using a gradient on the filter layer's mask.
4. Add a Levels filter layer for final output mapping: Layer > New Filter Layer > Colors > Levels. Set output black to 10, white to 245 to leave headroom for print.
5. Save as XCF: File > Save As > project.xcf. The filter graph is serialized inside.
6. Reopen and verify: Close GIMP, reopen project.xcf. Each filter layer remains editable — sliders, curve points, mask, blend mode all intact.

Practical check: Rename project.xcf to project.xcf.gz, gunzip, and open in a text editor. Search for gegl:curves or gegl:color-balance — you'll see the serialized operation graph with your exact parameter values.

Trade-offs and Limitations

Area	Reality	Mitigation
Backward compatibility	GIMP 2.8 and earlier cannot read XCF files with GEGL filter layers; they prompt to flatten or discard.	Keep a flattened copy if collaborating with older versions.
Legacy filters	Some Script‑Fu \"Artistic\" filters (e.g., Oilify, Cubism) are not ported to GEGL and remain destructive‑only.	Check the filter list under Layer > New Filter Layer; only GEGL‑backed filters appear.
OpenCL numerical variance	GPU path may produce sub‑pixel differences vs CPU.	Disable OpenCL (Edit > Preferences > System Resources > Use OpenCL) for pixel‑perfect reproducibility; restart GIMP after toggling.
Memory growth	Each filter layer caches intermediate tiles; 32‑bit float images with many layers can exceed 4 GB RAM.	Monitor via Edit > Preferences > System Resources > Tile cache size; consider 16‑bit float for large work.
Undo granularity	Dragging a slider creates one undo step per mouse release, not per value change.	Release the mouse deliberately; use numeric entry for precise, single‑step adjustments.

Export Reality Check

Filter layers exist only in XCF. File > Export As > PNG/JPEG/TIFF/PSD flattens the graph — the filters bake into pixels. The exported file has no live filters. If you need the editability later, you must keep the XCF. This is by design: external formats do not have a standard for serializing GEGL operation graphs.

Actionable Next Steps

1. Open GIMP 2.10+ (or 2.99 development build). Create a 16‑bit float image, add a Curves filter layer, push the curve hard, and confirm no banding in the histogram (Windows > Dockable Dialogs > Histogram).
2. Add three more filter layers (Levels, Gaussian Blur, Noise Reduction). Save as XCF, close, reopen — verify every slider is still live.
3. Export to PNG, reopen the PNG, and confirm the filters are baked (no filter icons in Layers dialog).
4. If you hit lag on slider drag, reduce tile cache or disable OpenCL; benchmark with a 4000×3000 16‑bit image and five filter layers — expect 200–800 ms full render on modern CPUs.

The engineering decision to model filters as GEGL graph nodes rather than pixel iterators is what makes this workflow possible. It's not magic — it's a deliberate architecture choice that keeps your edits editable, your bit depth honest, and your pipeline scriptable.