On this page
Chapter 19 · Limitations & decision guide
Every tool is a set of trade-offs, and the honest way to choose one is to know exactly what it cannot do. This chapter collects the limitations that are confirmed rather than rumoured, separates architectural limits from missing features, and then maps them onto real job types so you can decide quickly whether Photopea fits the work in front of you.
Confirmed missing features
These are capabilities that a Photoshop user will reach for and not find. They are not bugs and they are not on a public roadmap; they are absent by design or by the constraints of the platform.
| Missing capability | Impact | Workaround |
|---|---|---|
| CMYK colour mode with ICC profiles | Cannot produce a print-ready CMYK file with a specific press profile | Work in RGB, convert in Affinity Photo, Photoshop or a RIP at the print house |
| History brush | Cannot paint from a previous history state | Duplicate the layer before destructive edits and paint on the copy |
| Real print output | No Print dialog; print menu exports PDF instead | Export PDF or TIFF and print from a desktop application |
| Native plugin support (.8bf) | Cannot load Photoshop plugins such as Topaz, Nik or On1 | Use the iframe-based plugin API, which requires the plugin to be written for Photopea |
| Real-time collaboration | Two people cannot edit the same document simultaneously | Share storage, take turns, or use Figma for concurrent work |
| Non-destructive RAW develop module | The Camera Raw filter is partial; no full develop pipeline | Develop in Lightroom, darktable or RawTherapee, then open the TIFF or PSD |
| Autosave and crash recovery beyond snapshots | Unsaved work can be lost | Save to disk or cloud frequently; snapshots are roughly five-minute intervals |
| Shortcut remapping | Cannot change key bindings | Switch to a US keyboard layout while editing |
| Video editing | Animation is frame-based, not a video editor | Export frames and assemble in a video tool |
| 3D layers and 3D rendering | No 3D workspace | Use Blender or a dedicated 3D tool |
| Variable font axis control | Cannot manipulate variable font axes | Use static instances, or set up the type in a browser or InDesign |
| Colour-managed soft proofing | No soft proof against a press profile | Proof in a colour-managed application |
Architectural limitations
These are not missing features that could be added; they are consequences of running in a browser tab. They will improve as browsers improve, but they will not disappear.
| Constraint | Why it exists | Practical effect |
|---|---|---|
| Memory ceiling per tab | Browser process memory limits | Very large layered documents fail to open or crash mid-edit |
| No silent disk access outside Chromium | File System Access API is Chromium-only | Firefox and Safari users get download-based saves |
| No native printing | Browsers do not expose a colour-managed print pipeline to pages | Print is always an export-then-print workflow |
| Cold start requires network | No active service worker cache | Offline editing works within a session but not from a cold start |
| Single document per tab | Application architecture | No tabbed multi-document workspace; open a second browser tab instead |
| GPU-dependent performance | Filters use WebGL | Integrated graphics and older machines are noticeably slower on large blurs |
| AI features are server-side | Models run on Photopea's infrastructure | Requires network and credits; not available offline |
Photopea can open a CMYK PSD and can convert a document to CMYK, but it does not ship CMYK ICC profiles and does not offer a colour-managed CMYK workflow with a chosen press condition. What you get is a naive conversion, not a press-ready separation. For a flyer that will be printed on an office laser it does not matter. For anything going to a commercial press with a specified profile — FOGRA, GRACoL, SWOP — it does matter, and the conversion must happen elsewhere. This is the single most consequential limitation for print designers and it is frequently understated in reviews.
Where Photopea is genuinely strong
The limitations list is long, but so is the strength list, and the strengths are concentrated in exactly the tasks most people actually do.
Opening a PSD is the headline. Photopea's PSD engine preserves layers, groups, masks, clipping masks, layer styles, smart objects, adjustment layers and editable text with a fidelity that no other browser editor approaches. If a client sends a layered PSD and you need to change one word of copy or swap one image, Photopea does it in a browser tab without a licence. That single use case justifies the tool for a large number of people.
Format breadth is the second strength. PSD, PSB, XCF, Sketch, Figma, XD, INDD, PDF, AI, RAW, TIFF, PNG, JPEG, WebP, AVIF, GIF, BMP, SVG, EPS and more, in and out, with no watermark. A designer receiving files from five different clients in five different formats can open all of them in one place.
Zero install is the third. On a locked-down corporate laptop, a library machine, a Chromebook or a borrowed computer, Photopea is available immediately. That is not a convenience feature; for some people it is the only option.
The fourth strength is that the free tier is not crippled. Full editing engine, full export, no watermark. The paid tier buys AI credits, storage and a commercial licence, not access to the tools.
Use-case fit
| Job type | Fit | Reasoning |
|---|---|---|
| Editing a client's layered PSD | Excellent | Best-in-class PSD fidelity in a browser; no licence needed |
| Social media graphics and thumbnails | Excellent | Fast, template-friendly, exports every web format |
| Product photo cleanup and background removal | Very good | Remove BG and local healing are strong; credits are cheap |
| Web UI mockups | Good | Vector and text tools are capable, but Figma is better for systems and handoff |
| Photo retouching for print | Fair | Retouching is fine; the CMYK and soft-proof gap is the blocker |
| Commercial print production | Poor | No press-ready CMYK, no soft proofing, no print output |
| Large-format poster work | Poor | Memory ceiling bites on very large canvases |
| Motion graphics and video | Poor | Frame animation only; no video timeline |
| Team design systems | Poor | No real-time collaboration, no component library |
| Batch format conversion | Very good | Batch processing and Actions handle repetitive conversion well |
Competitive position
Against Photoshop, Photopea loses on colour management, plugin ecosystem, print pipeline, 3D, video, collaboration and raw performance. It wins on cost, install time, format breadth for non-Adobe files, and the fact that it opens PSDs without a subscription. For a freelancer who touches Photoshop files occasionally, that is a decisive trade.
Against GIMP, Photopea wins on PSD fidelity, interface modernity and format support. GIMP has a longer feature tail, a plugin ecosystem and no memory ceiling, but its PSD import is lossy and its interface is a barrier for anyone trained on Adobe. Photopea is the better choice for anyone who works with other people's Photoshop files; GIMP is the better choice for someone who wants a free desktop application and does not care about PSD round-tripping.
Against Affinity Photo, Photopea wins on price and availability and loses on colour management, performance and print production. Affinity is a one-time purchase with a real CMYK pipeline and no subscription; if print is your business, Affinity is the better buy and Photopea is the wrong tool.
Against Figma, the comparison is not really competitive because the products aim at different work. Figma is a collaborative interface design tool with a component system; Photopea is a raster and layered-document editor. For UI work Figma wins decisively. For editing a photograph Figma is not a candidate. The two coexist in most modern workflows.
A decision rule
If the work is a layered file that someone else made, or a web-bound image that needs editing now, on a machine you do not control, Photopea is the fastest correct answer and often the only one. If the work is going to a commercial press, needs a specific CMYK profile, involves very large canvases, requires plugins, or needs two people in the same file at once, Photopea is the wrong tool and no amount of workaround changes that.
The useful framing is not "is Photopea as good as Photoshop" but "which of my jobs does Photopea finish correctly, and which ones do I route elsewhere". For most independent designers the split is roughly eighty per cent Photopea, twenty per cent a desktop tool for print and heavy compositing. Knowing where that line falls is the whole point of this reference.
Chapter 20 documents the sources behind every claim in this reference, including where sources disagreed and how the disagreement was resolved.