Compositor: The Mac Image Editor That Wins by Refusing to Become Photoshop

A native Swift compositing app built around layers, non-destructive edits, and ruthless scope control. The real story is not feature count. It is how the product’s architecture keeps the workflow fast, light, and familiar.

9 min read • View on GitHub • More from robbietilton

A wide desk scene shows a compact, precise macOS image editor beside a hulking, tangled legacy suite machine. The smaller tool looks engineered for focus, while the larger one is crowded with cables, panels, and excess parts. It explains the article’s central idea that restraint can be a product advantage.
Compositor’s bet is that a narrower tool can feel more professional because it avoids the sprawl that slows down the workflow.
Key Takeaways

A Photoshop Alternative That Wins by Being Smaller

Compositor is not trying to beat Photoshop at being Photoshop. It is trying to keep the parts of that workflow that matter, then cut away the rest. That choice changes everything, from the interface to the memory model.

Adobe Photoshop costs too much and tools like GIMP don't feel familiar enough for me to stay in flow. That's why I built Compositor. The goal was to create a full-featured image editor that is completely free and open source.

Robbie Tilton, Creator / Designer · Compositor – The Photoshop alternative for Mac
ToolPlatformLicensingWorkflow focusTypical feel
CompositormacOSMIT open sourceCompositing, layers, masks, non-destructive editsNative, focused, restrained
PhotoshopmacOS, WindowsCommercial subscriptionGeneral-purpose pro imagingPowerful, sprawling, heavyweight
GIMPCross-platformOpen sourceBroad raster editingCapable, less familiar to Photoshop users
Affinity PhotomacOS, WindowsCommercial purchasePro photo editingPolished, feature-rich
Pixelmator PromacOSCommercial purchaseNative Mac image editingFast, modern, broad

That table is the point. Compositor does not win by broadest feature list. It wins by matching a narrower job to a cleaner implementation, which is why it can feel serious without feeling bloated.

What Compositor Keeps, What It Leaves Out

The app is tuned for compositing work: layers, masks, transforms, blend modes, adjustment layers, selection tools, and pixel-level retouching. It aims for the familiar Photoshop-shaped workflow, but only the pieces that support finishing an image.

That discipline is why the app feels coherent. A narrow product can remove whole classes of edge cases, and every removed edge case is one less place for the interface to wobble.

The undo model is not a simple stack. It is a graph of shared snapshots, which keeps history useful without copying every pixel every time.

The Data Model Is the Product

Compositor treats an image session like structured state, not a single bitmap. Layers carry transforms, masks, adjustments, and imported assets as separate pieces of document logic.

struct ImageLayer {
    var transform: LayerTransform
    var blendMode: BlendMode
    var mask: Mask?
    var adjustment: AdjustmentLayer?
    var asset: ImportedImage?
}

// Allocate pixels when painting begins, not when adding an empty layer.

That last line matters. Empty layers are cheap because the app does not spend memory on pixels until the user actually paints. The result is a document model that behaves more like a composition graph than a pile of cloned images.

A close-up compositing stack shows transparent layers, a mask sheet, a transform grid, and a sealed base layer of source pixels. Beside it, a rail of connected history nodes shows shared snapshots that fork only when an edit changes something. It explains how the app keeps undo rich while preserving memory.
Compositor keeps history light by sharing what has not changed and only breaking away when a layer actually mutates.

Undo That Does Not Punish You

The undo system is the most revealing part of the project. Instead of treating every action as a full copy of the world, Compositor stores snapshots and reuses immutable image data where it can.

That keeps history responsive, but it also makes the memory cap meaningful. When retained state grows past the limit, the history can be trimmed without collapsing the user’s sense of control.

This is a product decision, not just an optimization. Rich undo only matters if it stays usable after dozens of edits, not just in a demo.

Why SwiftUI Works Here

SwiftUI is a surprise only if you assume pro software has to look old-school to be credible. Compositor uses it for panels, inspectors, and orchestration, then pushes the hot path into lower-level rendering code.

LayerRoleWhy it fits
SwiftUIInterface and state orchestrationFast to iterate on panel-heavy app structure
SwiftDocument logic and app coordinationClear model code and modern app architecture
C and MetalPixel loops and GPU workKeeps image operations responsive
Core ImageImage processing supportUseful for filters and rendering primitives

That split is the architectural trick. The UI stays native and expressive, while the expensive work gets its own lane.

How the Render Pipeline Stays Fast

Compositor avoids making the canvas one giant monolith. Rendering is tiled, which means the app can refresh the parts of the image that matter instead of dragging the whole document through every interaction.

Swift coordinates the app, C handles tight pixel work, and Metal plus Core Image handle the GPU-heavy pieces. The user experience benefit is simple: the editor stays alive under pressure.

ApproachCostUser effect
Monolithic full-canvas redrawsHighLaggy pans, slow brush feedback
Tiled renderingLocalizedSmaller updates, steadier interaction
Snapshot sharingSelectiveUndo stays rich without exploding memory

Where Compositor Fits in the Landscape

The cleanest way to describe Compositor is as a minimalist pro tool for Mac users who want Photoshop-shaped workflows without the baggage. It sits near Pixelmator Pro and Affinity Photo in seriousness, but its open-source, narrowly scoped stance makes it feel more opinionated.

That opinion matters. Most image editors try to become everything. Compositor picks the pieces needed for finishing work and stops there.