If you have been hunting for an open source Photoshop alternative for Mac in 2026, one name now dominates the conversation: Compositor. Built by developer Robbie Tilton as a personal escape from Adobe’s subscription pricing, this native Swift image editor has collected more than 17,000 GitHub stars in barely five weeks — and it does its best work exactly where Photoshop users actually spend their time: layers, masks, selections, and post-processing. In this deep-dive we cover what Compositor is, what it can and cannot do, how to install it, why developers are watching it, and the honest limitations you should know before handing it client work.
What Compositor is
Compositor is a free, open source image editor for macOS that targets one workflow with uncommon focus: compositing and post-processing — the bread and butter of digital illustration, marketing graphics, product imagery, and photo retouching. Tilton’s own words explain the motivation: “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 numbers tell the adoption story. The Compositor GitHub repository was created in mid-September 2026 and, as of this week, holds roughly 17,600 stars with more than 1,700 forks, 505 commits, and 50 releases. Development pace is relentless — commits were landing as recently as today. It is MIT-licensed, so there is no paid tier, no feature-gated “pro” version, and no account to create.
Two architectural facts explain much of its appeal. First, it is a genuinely native app: written in Swift against Apple’s own frameworks, running only on Apple silicon Macs with macOS 26 or later. Reports put the app at around 12 MB — staggeringly small next to Adobe’s multi-gigabyte installs — and it launches essentially instantly. Second, it is deliberately local: no login, no cloud sync, no telemetry. A local editor that does not phone home is increasingly rare in creative software, and it matters for teams with client confidentiality obligations.
What Compositor can do: the feature tour
This is not a tech demo with a star count propping it up. The feature list from the project’s README reads like a serious compositing tool.
Layers and compositing
Layers and folders with opacity, Photoshop’s full set of blend modes, layer masks (paint, fill, invert, blur, feather), clipping masks and folder masks. Adjustment layers include Hue/Saturation, Levels, Curves, Exposure, Gradient Map, Color Balance, Gaussian and Motion Blur, and Noise — most of what a working compositor reaches for daily. Layer effects (Stroke, Drop Shadow, Color Overlay, Inner/Outer Glow, Inner Shadow) render on the GPU and stay editable. Merge Down, Merge Layers and Merge Group are all present, with Photoshop-style shortcuts throughout — remappable in Edit > Keyboard Shortcuts.
Selections and retouching
Rectangle and Ellipse Marquee, Freehand and Polygonal Lasso, Magic Wand and an Object selection tool, plus Select Subject, and Expand, Contract and Feather on any selection. Content-Aware Fill is included — and can extend an image past its edges, the generative-expand trick without the generative-AI price tag. For retouching: a brush with size, hardness, opacity and tablet pressure support, a content-aware Spot Healing Brush, Clone Stamp, Blur tool, and editable Gradient and Shape tools that stay vector-like instead of being rasterized.
Adjustments, filters and raw
A Camera Raw filter handles light, color, curves, color mixer, color grading, detail, optics and geometry in a panel beside the canvas — with per-section resets. The standard arsenal is all here: Levels with Auto, Curves, Exposure, Gradient Map, Grain, Vignette, Bloom/Glow, Dither, Scanlines, Tonal Contrast, Lens Correction, and Remove Background, with live previews and a “Last Filter” shortcut (Ctrl+Cmd+F) to re-run the previous filter with the same settings.
Canvas, files and workflow
Multiple projects in tabs. Photoshop-style keyboard shortcuts everywhere, plus a Command-F “Search Commands” palette in the Raycast/Obsidian style — type a command name and run it. Fullscreen canvas mode, rulers and guides, a layout grid, a navigator minimap at high zoom, and sharp downsampling when zoomed out.
File support is practical rather than exhaustive: JPEG, PNG, HEIC, TIFF, WebP, SVG, camera RAW (with a develop step first), and Photoshop PSD and PSB — with a realistic, documented limitation: 8-bit RGB only, not CMYK. Photoshop folders, masks, blend modes and simple horizontal text stay editable; other vectors and vertical text become pixels, and the app shows a conversion report before applying anything. That honesty about PSD fidelity is exactly the kind of detail a working professional needs, and it is refreshingly explicit.
Getting Compositor installed and running
Installation takes under a minute on a supported Mac. The requirements: macOS 26.0 or later on Apple silicon — Intel Macs and older macOS versions are not supported.
- Download from the developer’s download page or the latest GitHub release, or install with Homebrew:
brew install --cask robbietilton-compositor
- Open the DMG, drag Compositor to Applications, and launch — no account creation, no license key, no first-run upsell.
- Open a test PSD to verify your round-trip fidelity before touching production files. Watch the conversion report on first import.
- Remap any shortcuts that clash with your muscle memory in Edit > Keyboard Shortcuts, and try Command-F Search Commands — it is the fastest way to learn the app.
- To build from source: open
Compositor.xcodeprojin Xcode 26 or later and run the Compositor scheme. The project is MIT-licensed, so modifications are yours to make.
Updates are automatic: signed and notarized builds with an in-app updater. One measured fact worth knowing: the app checks for updates at most once a day when opened, against an update feed hosted on GitHub. That is the app’s only network behavior — no analytics, no tracking, a claim that holds up because the whole codebase is open for audit.
Why this open source Photoshop alternative for Mac is winning in 2026
Three forces are converging. First, subscription fatigue is real and Photoshop is its poster child: Adobe’s photography plan costs roughly $23 a month — over $275 a year, every year, forever — just to keep opening the files you already made. Compositor costs zero, forever, and you own the workflow.
Second, the “good enough” threshold for most creative work is lower than Adobe’s marketing suggests. Independent coverage has scored professional-use parity below 50% — AI and generative features are essentially absent — but the honest counterpoint is that compositing, retouching and post-processing were always the core of Photoshop for most users, and Compositor nails that core natively at 12 MB.
Third — and this is the angle most coverage underplays — Compositor is agent-native. A .comp project is simply a folder of PNG layers plus a manifest file, and an open project refreshes live as those files are written. That means scripts and AI agents can build and edit images programmatically, with a documented writing-comp-files.md guide. In an AI tools landscape where everything wants an API, a local image editor with a file-based project format is quietly radical: it gives you scriptable image generation and editing with no per-call pricing. Browse our AI tools directory for more tools in this automation-friendly mould.
From our experience: build-vs-buy economics for creative tooling
At MTD Technologies we ship client work where the tooling bill is a real line item. The math that makes Compositor interesting is not “free versus $23/month” — it is “free versus $23/month times every seat times every year.” A ten-person content team pays close to $2,800 a year for Photoshop access; across a five-year horizon that is roughly $14,000 of pure tooling rent for software you never own. A native, maintained, MIT-licensed alternative with no seat licensing changes that arithmetic fundamentally — even before you factor in that Compositor installs in seconds, launches instantly, and carries no admin overhead for license management.
The deeper practitioner point is about where open source creative tools finally got good. GIMP’s problem was never features — it was feel: a GTK UI and a shortcut map that fought Photoshop muscle memory. Compositor’s bet is that familiarity is the feature. Photoshop-style shortcuts, Photoshop blend-mode order, drag-to-scrub value labels — the interface speaks the dialect your designers already know. That is why adoption is fast: the learning curve is a weekend, not a quarter.
There is also a maintenance story worth noting. One developer, 505 commits, 50 releases, and a steady stream of issues being worked — this is the cadence of a project being actively sharpened, not abandoned. For agencies evaluating dependency risk on open source creative tools, that release velocity is the metric that matters more than the star count.
Watch-outs: when Compositor is not the right call
Honest tooling advice cuts both ways, so here is where we would not recommend it:
- Print production needing CMYK: PSD import is 8-bit RGB only. If your deliverables go to press with plate separations, this is a hard stop — stay with Photoshop or Affinity.
- Windows or Linux teams: Compositor is macOS-only, Apple silicon only. Mixed-OS teams need a cross-platform answer.
- Generative AI workflows: there is no generative fill, no AI upscaling, no text-to-image. The developer has deliberately paused AI features — he closed a community PR adding Gemini-based generative fill to rethink how AI should fit the app in a v2. If AI generation is central to your pipeline, you will need a companion tool.
- Single-maintainer risk: this is a one-person project. The upside is velocity and a coherent vision; the downside is the classic bus-factor problem. Because it is MIT-licensed with an open Xcode project, the community could fork and continue it — that exit hatch exists, but a risk plan should acknowledge it.
- Localization: English only, and the maintainer is not accepting translation PRs. Fine for most teams; a blocker for some.
- Codebase auditability: independent reporting notes the ~37,000-line Swift codebase is largely AI-assisted — one outside developer described it as “decidedly not for human consumption.” That is not a criticism of how it runs, but if your security posture requires readable source for audit, know what you are getting.
Responsible-use note: keep it local, keep it auditable
Compositor is a local, single-user editor with effectively no network path — the update check aside — which makes its trust story unusually simple: there is no cloud to leak your client’s unpublished artwork through. That said, project files you receive from others are executable-adjacent input; treat downloaded .comp files like any untrusted attachment until you have verified them. And because the codebase is open, the privacy claims (“no login, no account, no tracking”) are checkable rather than take-on-trust — a property worth valuing in creative software, where cloud-linked editors increasingly train models on your work.
Frequently asked questions
Is Compositor really free?
Yes — completely. Compositor is MIT-licensed with no paid tiers, no in-app purchases, no trial clock and no account. The only thing it will ever ask of your network is a once-a-day update check against its GitHub-hosted feed.
Can Compositor open Photoshop PSD files?
Yes, including large PSB files — layers, folders, masks, blend modes and simple horizontal text stay editable, and a conversion report shows before anything is applied. The hard limitation is color space: 8-bit RGB only, no CMYK. Print workflows with press profiles should not migrate.
Does Compositor work on Windows, Linux or Intel Macs?
No. It requires macOS 26.0 or later on Apple silicon. The native-Swift, 12 MB footprint that makes it fast is also what makes it platform-exclusive. Windows and Linux users needing a free alternative should look at GIMP 3.x or the browser-based Photopea.
How is Compositor different from GIMP?
Familiarity and feel. GIMP is powerful but its interface and shortcut map fight Photoshop muscle memory; Compositor was built around the compositing workflow Photoshop users already know — layers, masks, blend modes, Photoshop-style shortcuts — in a native Mac app a fraction of the size.
Is Compositor safe for professional client work?
For screen-first deliverables (web, social, product imagery, app assets), yes — with the usual diligence: test your PSD round-trips, keep versioned backups, and note the single-maintainer risk in your tooling plan. For CMYK print production or heavy plugin ecosystems, it is not there yet.
Bottom line: Compositor is the first open source Photoshop alternative for Mac that feels like it was built by someone who actually ships compositing work — because it was. If your team lives on Apple silicon and your deliverables are pixels, not plates, this is the free editor to evaluate this year. And if you are exploring how AI agents and scripted image pipelines fit your creative workflow, that is exactly the kind of automation architecture we build at MTD — talk to us about what your team needs.