Affinity vs GIMP: choose by workflow and editable files

Both have a free route. The useful differences are the account requirement, Linux support, RAW workflow and which parts of your project stay editable.

Two matte print stacks compare pears on linen with orange and graphite cut-paper shapes, backed by orange cards on cream.

Choose Affinity for a project that combines RAW development, photo editing, vector artwork and page layout; choose GIMP for native Linux editing, an account-free desktop workflow or an established XCF composition. Both now have a free route for individuals. I'd favour Affinity when the photograph is one part of a larger design, and keep GIMP when the important work is refining a mask, retouching pixels and preserving a clear layer stack.

The deciding question is what you must change next week. A finished PNG can look right in either app while losing the live text, RAW settings or effects that made the original project useful.

Which editor fits your next job?

Your next jobMy starting choiceWhy it matters
Edit on a Linux desktopGIMPNative Linux support; no supported native Affinity Linux build.
Retouch an existing masked XCFGIMPKeep the existing layers and effects in their native project.
Develop RAW, then build a designed pageAffinityDevelop, Pixel, Vector and Layout work can stay in one app.
Prepare a CMYK publicationAffinityCMYK documents, layout and print checks belong to the same workflow.
Continue the same project on iPadAffinityThe new desktop and iPad apps share .af files; check the iPad feature limits.
Work without a service accountGIMPNo Canva account or online activation step.
Return an editable PSD to somebody elseCheck the required objects firstNeither opening the file nor retaining some layers guarantees a faithful round trip.

GIMP's official desktop builds cover Windows, macOS and GNU/Linux. Affinity's supported platforms are Windows, macOS and iPadOS. A Linux compatibility-layer experiment adds another dependency; I'd choose GIMP if native Linux support is a condition of the job.

Free Affinity, Affinity Photo 2 and the account requirement

The current unified Affinity app is different from the older Affinity Photo 2, Designer 2 and Publisher 2 suite. Comparing a new user's free GIMP download with an old Affinity licence price gives the wrong answer. Affinity's Pixel, Vector and Layout tools are free for individuals with a Canva account; Canva AI needs a premium Canva plan. Ordinary editing doesn't require that paid plan.

Affinity requires an internet connection for downloading and activation, then allows extended offline use. Help, stock services, integrations and AI have separate online requirements. Existing V2 licences remain valid, but the V2 apps won't receive future updates. Keep an untouched copy of an old project before migrating it.

GIMP is free software and permits commercial image work. It can be used without a service account. I'd put that distinction ahead of the old paid-versus-free argument: it affects access to your tools, whereas paying nothing doesn't tell you which editor fits the document.

Layers, masks and effects: what survives a revision?

Affinity's adjustment layers and live filters keep changes separate from the underlying image. That is useful when a portrait needs a different tonal treatment after the layout is finished: revisit the adjustment or its mask, rather than rebuilding the image from an earlier export. Keep the .af master with those objects intact.

That doesn't make every operation reversible. Painting directly into a pixel layer, rasterising an object or flattening a document changes what you can edit. Choose an adjustment or live filter when you need its settings later; keep a source layer before committing a destructive step. A saved project is only as flexible as the structure you retain.

GIMP 3 also has editable filters. Most eligible GEGL filters can remain as layer effects saved inside XCF. Leave Merge Filter off in the filter dialogue, then use the layer's fx controls to revisit the effect. Other plug-ins aren't automatically live effects, and exporting to PSD doesn't carry those GIMP effects across as editable effects.

GIMP 3.2 adds vector and link layers, alongside editable text. It also supports an adjustment-style workflow by putting a non-destructive filter on an empty Pass through layer group. Calling GIMP a purely destructive editor misses these options.

Watch the layer type. In GIMP 3.2, Layer > Rasterize enables destructive pixel edits on text, vector and link layers. Revert Rasterize restores the original layer type and clears the destructive edits. For a cutout, I'd keep the edge in a layer mask whose thumbnail is easy to identify, with the source image beneath it, rather than erase pixels and rely on Undo.

GIMP 3.2 Curves dialog: Value curve raised by one control point at Input 128, Output 150, with Preview checked and Merge filter unchecked
Leave Merge filter unchecked to retain an editable correction; the curve values shown are an example rather than a recipe for every photograph. Open the Curves filter controls at full size.

Selections for a collage with many cutouts

For a collage with many cutouts, I'd compare the time needed to reach a clean, editable mask. Affinity offers Select Subject and Object Selection as automatic starting points. Its current Select Subject instructions require a downloaded machine-learning model and a Canva premium plan, so include that condition if automatic subject selection is your reason to switch.

GIMP's Foreground Select starts with a rough outline and painted foreground hints, followed by a preview you can refine. Keep the selection as a layer mask and inspect hair, gaps between objects and colour spill against both light and dark backgrounds. Try several typical source images: a quick first selection can still need substantial edge work. The comparison that matters is the usable cutout and its later adjustment.

RAW: one app or a separate developer?

Affinity has built-in RAW development. Open a supported camera RAW through File > Open, adjust it in Develop Studio, then choose the Output before clicking Develop. The three RAW output choices have different consequences:

  • Pixel layer: the development becomes pixels. The original camera file stays separate, but this layer doesn't retain live RAW settings.
  • RAW layer (embedded): the RAW is copied into the document and remains editable. I'd choose this when moving the project between devices.
  • RAW layer (linked): the document refers to the RAW at its existing location. Keep that source available when moving or archiving the project.

GIMP hands RAW development to software such as darktable or RawTherapee. The darktable integration returns the developed image to GIMP; the XCF then stores your pixel-editing composition. Keep the RAW and the developer's settings separately, because changing white balance in the RAW developer is a different operation from correcting a rendered layer.

I'd choose Affinity for repeated RAW-to-retouch revisions within one document. GIMP remains a sensible choice if darktable already handles your RAW workflow and you want GIMP for the selective corrections that follow. Check support for your actual camera model before committing a shoot to either route.

For multi-shot photography, Affinity desktop also provides HDR Merge, Focus Merge, macros and batch processing. Those are concrete reasons to prefer it for exposure brackets, a focus stack or repeated exports. They don't establish that it will process every camera sequence more accurately; use the actual source files when checking alignment and the finished edges.

Text, vectors and print change the recommendation

A photo with a headline is still a manageable GIMP task. A brochure with linked pictures, substantial typography and repeated page changes gives Affinity's combined studios a clearer purpose. You can move between pixel work, vector design and layout without rebuilding the job as a succession of flattened pictures. I'd choose around the document you must maintain, rather than the number of tools on a feature list.

For a print publication, Affinity supports CMYK/8 documents, ICC profiles, bleed and a Preflight panel. Agree on the printer's profile, dimensions, bleed and PDF requirements before export. A particular resolution or PDF/X preset isn't a universal answer for every print job.

GIMP's working image modes are RGB, Grayscale and Indexed; choosing a CMYK colour in a selector doesn't turn the document into a CMYK working document. You can set Image > Color Management > Soft-Proof Profile, then enable View > Color Management > Proof Colors to preview the requested output profile. Soft-proofing simulates that output; it doesn't create a complete page-layout or print-delivery workflow. If a lab requests an RGB photograph, follow that specification instead of converting simply because the destination is paper.

GIMP offers a different kind of flexibility through scripts and plug-ins. Its current plug-in architecture supports Python and Script-Fu, but the 3.x API changes mean older plug-ins need updating. If an extension is central to your workflow, confirm its supported GIMP version, operating system and packaging before treating it as a reason to switch. Extensibility is useful when the required extension is maintained.

What the PSD compatibility test actually shows

The 12 October Testy run compared 309 small PSD and PSB feature files, totalling 49.6 MB, against Photoshop 27.10.0. Affinity 3.3.1.4940 had a 77.4% mean perceptual match; GIMP 3.2.6 had 43.7%. Affinity opened 304 of the 309 files, while GIMP opened all 309. Opening more files clearly didn't mean rendering their contents more faithfully.

Testy result, same runAffinity 3.3.1.4940GIMP 3.2.6
Mean perceptual match77.4%43.7%
Mean layer data retained in PSD save84.1%46.7%
Text objects retained as text in PSD save0/430/43

This is one compatibility test, not a speed benchmark or an overall editor rating. Its feature-focused method removes cached renderings for the objects it scores. The figures aren't a success probability for a complex client document. My conclusion is narrower: Affinity is the stronger starting point here for PSD appearance and retained structure, but neither result justifies promising an editable Photoshop round trip.

Affinity's import settings help with a different stage. In Settings > General, Import PSD text as text rather than bitmap preserves imported type for editing in Affinity; Import PSD smart objects where possible controls supported smart-object imports. That wording matters. Successful import into an .af master doesn't establish that the same objects will export back to PSD intact.

If the recipient needs an editable headline, mask or smart object, check that exact requirement with a copy of the real document. Keep the received PSD, save a native master, export a separate exchange copy through File > Export, and have the recipient reopen it. Inspect both the appearance and the required editable objects before replacing anything.

iPad work needs the new app and the right master

The new Affinity for iPad uses the same .af format as desktop. It is a native touch and Apple Pencil route. New .af files can't be opened in the older V2 apps, so confirm the app generation at both ends before sending a project.

Shared files don't mean every desktop task is available on iPad. Current limitations include Batch, recording macros, Data Merge, Books and Astrophotography Studio. I'd keep a batch-dependent or astrophotography workflow on desktop until the required tools are available on the tablet.

GIMP's supported builds remain desktop builds. You can use an iPad as a display or transfer finished images, but that is different from a native iPad GIMP app. Keep an XCF for GIMP revisions and export a separate delivery image. A PNG can retain transparency and the finished appearance; it doesn't move the separate GIMP masks, live text and effect stack into Affinity.

Make the choice with one representative project

For an existing masked XCF, I'd finish in GIMP unless a specific Affinity tool solves a problem you already have. For a new RAW-and-layout project on Windows or Mac, I'd start in Affinity. Native Linux and account-free access settle the choice for GIMP; native iPad continuation favours the new Affinity apps.

Before moving a larger workflow, use a copy of one typical job. Include its real image dimensions, fonts, layer count, masks and effects. Make the next likely revision, save, close, reopen, and produce the required delivery file. Check a fine edge, change the headline and reopen the effect settings. For linked files, repeat after moving the project with its sources.

Judge responsiveness on that same computer and document: opening, brush response, a heavy live filter and final export stress different parts of an editor. A generic claim that one app is faster can't tell you whether your particular layer stack will remain pleasant to edit. I'd choose the editor that preserves the revisions the job needs, then keep its native master alongside the finished export.

Elena Morris

Elena Morris

Elena Morris is the GIMP image-editing and compositing editor at TheGIMP.net. She writes about selections, masks and layers, restrained retouching, compositing and export.