HN Debrief

GIMP Development Update

  • Open Source
  • Design
  • Developer Tools
  • Product Strategy

The update says GIMP is pushing on three practical fronts. It is building a new project file format, keeping long-term backward compatibility for old XCF files, and continuing the shift toward modern editing features like non-destructive filters and autosave. The file format work drew the most technical interest because the team wants a more structured container that can save incrementally instead of rewriting the whole project every time. A maintainer explained that the real reason is tight integration with GEGL buffers, so edits can sync directly from memory to disk as you work. That is also why OpenRaster is not enough, even though it already uses a zipped-archive style and is supported today.

If you care about open, durable creative workflows, GIMP is getting stronger under the hood, especially around non-destructive editing and recoverability. But if your team needs fast onboarding or Photoshop-like ergonomics, the product risk is still the interface, not the core engine.

Discussion mood

Mostly negative on usability, with respect for the engineering and the project’s staying power. People like the open formats, offline use, reliability, and recent progress on non-destructive editing, but many still see the interface and default workflows as stubbornly hostile to newcomers and casual users.

Key insights

  1. 01

    GEGL integration is the real file-format story

    The new format is not just "zipped XML" for readability. It is being designed so GEGL buffers can sync pixel data directly between memory and disk during editing, which is what makes fast autosave and partial updates possible. That reframes the choice as an engine-level persistence change, not a cosmetic swap away from XCF.

    Watch the implementation details before judging the format from the container label alone. If your product has large mutable assets, the storage model needs to match the editing engine, not just pick a fashionable file format.

      Attribution:
    • cmyk_student #1 #2
  2. 02

    Save behavior hurts more because edits stay destructive

    The Save versus Export split would be easier to defend if project files preserved a rich editing state like users expect from modern creative tools. Commenters pointed out that XCF does not store undo history, and GIMP still pushes users into rasterizing decisions earlier than Photoshop. That makes the insistence on saving to the native format feel less valuable for everyday work than the interface suggests.

    A native project format only earns extra workflow friction if it preserves meaningfully more state. If it does not, users will treat every nag screen as product debt.

      Attribution:
    • account42 #1
    • barrkel #1
    • Joeboy #1
  3. 03

    The project is trying to open a UX lane

    A contributor described a more deliberate path for interface changes than the project gets credit for. There is a separate UX issue tracker, maintainers move workflow issues into it, and an extension platform is being built so alternates like PhotoGIMP can be installed more easily. The obstacle is not pure refusal. It is the classic problem of changing a mature tool without detonating existing workflows.

    For mature developer-facing products, extensions and optional modes can absorb a lot of UX tension that core redesigns cannot. If you need to modernize without breaking power users, give newcomers an easier on-ramp rather than forcing one default for everyone.

      Attribution:
    • cmyk_student #1 #2 #3
    • anfogoat #1
  4. 04

    Open files are a business continuity feature

    A small-business user made the strongest practical case for GIMP that had nothing to do with ideology. Canva makes it painful to back up original working files in bulk, while GIMP and Inkscape leave teams with assets they can store, migrate, and reopen without vendor permission. That turns file openness into operational resilience, not just a FOSS talking point.

    If your team creates long-lived design assets, include exportability and project-file ownership in tool selection. Convenience today can turn into archive and migration pain later.

      Attribution:
    • pinkmuffinere #1
  5. 05

    The bad reputation comes from tiny workflow ambushes

    The most persuasive complaints were small interaction failures that break flow, not grand arguments about taste. Losing canvas focus after using a panel and having the move tool select the layer under your cursor instead of the selected layer are both survivable once learned. They are also exactly the sort of surprises that make software feel irrational to everyone else.

    Do not dismiss small UX paper cuts because experts can work around them. A handful of tiny context switches can define the reputation of an otherwise capable product.

      Attribution:
    • anfogoat #1
    • two_handfuls #1
    • somat #1

Against the grain

  1. 01

    Save and Export are a legitimate distinction

    For a real editing application, separating project saves from flattened output is not eccentric. It protects users from quietly throwing away layers, filters, and other state, and some people find choosing Save or Export up front faster than digging through a format dropdown later. The problem is less the concept than how aggressively GIMP surfaces it in simple edit-and-close workflows.

    Do not copy complaints blindly from casual users into product design. If your software has destructive output formats, make the distinction clear, then remove unnecessary warnings after intent is established.

      Attribution:
    • flufluflufluffy #1
    • mort96 #1
    • em-bee #1
  2. 02

    Many people are using the wrong class of tool

    Several defenses of GIMP argued that much of the frustration comes from treating a full image editor like a lightweight annotation app. If the actual job is adding text to a family photo, tools like Pinta, KolourPaint, Figma, or Photopea may be a better fit. Judging GIMP by that use case misses the fact that it is trying to be closer to Photoshop than to MS Paint.

    Match tool complexity to the job before concluding the product is broken. For internal teams, standardize a simple editor for simple tasks and reserve heavier tools for people who need them.

      Attribution:
    • pessimizer #1 #2
  3. 03

    Expert users value stability over reinvention

    Long-time users described GIMP as learn-once software that stays put, rarely crashes, and avoids the churn that makes some commercial creative tools feel unstable over time. From that angle, the same conservatism that annoys newcomers is part of why existing users trust it in production workflows. A drastic redesign would not be a free win.

    When you modernize a mature product, measure the cost to expert throughput explicitly. Stability and predictable workflows are product features, even when they look like inertia from the outside.

      Attribution:
    • Liftyee #1
    • jcarrano #1
    • sho_hn #1
    • reactordev #1

In plain english

FOSS
Free and open-source software, software whose source code can be used, studied, modified, and shared by anyone under its license.
GEGL
Generic Graphics Library, the image-processing engine GIMP uses for pixel operations, color handling, and non-destructive effects.
JPEG
A common compressed image format mainly used for photos, which usually does not preserve editing layers or advanced project state.
OpenRaster
An open layered image file format that stores project data as files inside a compressed archive.
PhotoGIMP
A customization package for GIMP that changes shortcuts, layout, and defaults to feel more like Adobe Photoshop.
UI
User Interface, the visual and interactive parts of a software product that people use directly.
UX
User experience, how a product feels to use in practice.
XCF
GIMP’s native project file format, which stores editable image data and project structure.
XML
Extensible Markup Language, a text-based format for structured data that is often used inside document and project containers.

Reference links

GIMP design and ecosystem

  • GIMP UX design issue tracker
    Shown as the place to file workflow and interface feedback for GIMP.
  • PhotoGIMP
    Referenced as a Photoshop-like customization package that could become easier to install via GIMP’s future extension platform.

File formats and storage references

Alternative tools and comparisons

Broader ecosystem references