Photopea Local: Can You Run or Self-Host It?

What does Photopea allow locally, and what doesn't it?

People searching for photopea local usually want one of two things: to use the editor without a connection, or to run their own copy on a machine they control. Photopea's own homepage speaks to the first in a narrow sense. Under a heading called Fully Local, it says there are no uploads, that Photopea runs on your device using your CPU and your GPU, and that files open instantly and never leave your device.

What the homepage does not offer is a download or a server package. The codebase is closed-source, which sets Photopea apart from GIMP and Krita, and the free tier is ad-supported. As of October 2026, Premium is listed at $5/mo and removes ads. The editor has been maintained by a single creator, Ivan Kutskir, since 2013, so decisions about distribution rest with one person rather than a committee.

So the short answer is split. Processing on your own hardware is exactly what the vendor advertises, while hosting the editor on your own server is not something the homepage presents. Read the terms and the API page on the official site before building a workflow around either idea, and do not deduce permission from the fact that the editor happens to run inside a browser tab you control.

Is working offline the same as hosting it myself?

No, and the two are easy to blur. Working offline means the app keeps running when your connection is gone, usually because a service worker stored its files in the browser. Photopea can be installed as a windowed app from Chrome or Edge, but it registers no service worker, so it does not cache itself for offline use. Each load still needs a live connection to the Photopea site.

Self-hosting is a different request. It means the files that make up the app are served from a machine you run, so no outside server is involved at all. Excalidraw shows how far apart the ideas sit: it works fully offline, with boards stored in IndexedDB, and teams who want collaboration kept internal can self-host its room server, which takes about 10 minutes. Photopea offers neither path.

Photopea's Fully Local wording refers to where your files are processed, not to where the app lives. That gives three separate questions with three separate answers. Is the work done on your device? Yes, according to the homepage. Does it run without a connection? No, each load needs one. Can you host it yourself? Nothing official says so. Anyone typing photopea local into a search box should work out which of the three they actually mean.

What happens when the network drops during an edit?

The vendor's description helps here. Because Photopea says it runs on your device with your CPU and GPU, the editing itself is not a round trip to a server: layers, masks and filters are handled by the page already open in front of you. That is a reading of the homepage, not a promise about every feature, so do not stake an important deadline on it.

The risk comes afterwards. With no service worker caching the app, reloading the tab, reopening the installed window or restarting the browser means fetching the editor again, and that fetch needs a connection. If the network is down at that moment, the editor will not load, and you should not count on getting an unsaved document back from a session you can no longer reopen.

A few habits follow from this. Save a PSD copy to your disk before any reload or before leaving a place with reliable Wi-Fi, since PSD is the main format Photopea reads and writes. Keep large projects modest too: the browser, not the network, sets the ceiling, and huge files with hundreds of layers typically max out around 2-3GB of browser memory.

Who actually needs to self-host Photopea?

Self-hosting makes sense for a company that wants every tool served from infrastructure it controls, or for a workstation with restricted or no internet access, where an editor that must reach the Photopea site on every load simply cannot start. For those readers the photopea local question has a blunt answer: nothing in the vendor's public description supports it, so ask the creator directly or choose software built for that setup.

For almost everyone else the question is moot. A freelancer opening a client's PSD once a quarter, a student, or a teacher running a Photoshop class without paying for licences only needs a browser and a connection. The installed app also works cleanly on Chromebooks, which makes it a practical fit for school design classes, provided the school network allows the connection.

Teams with other needs should look elsewhere. Photopea has no shared libraries, version history or commenting, so agencies that collaborate on files will miss them. People who want source code they can inspect and run themselves are better served by GIMP or Krita, both open-source, and Photopea can still open GIMP's XCF files, which eases moving between them.

Where can I find Photopea and similar editors?

The full entry sits at Photopea. It covers what the editor does: it opens and saves PSD, and the homepage also lists PNG, JPG, GIF, WEBP, SVG, PDF, AI, HEIC, TIFF and Figma files among those it opens, plus RAW formats such as DNG, CR2 and NEF. Layers, masks, filters and blend modes are all there, and the keyboard shortcuts mirror Photoshop's.

If you want to compare it with other browser editors, the photo editors that run in the browser roundup is the place to start, and the Design & Creative hub groups related tools. For a design tool where self-hosting is a real option, see Figma alternative free: self-host or browser picks. Both pages help if your goal is a tool that behaves the same with or without a connection.

Go in with realistic expectations. The homepage describes one-click background removal and text-based content replacement, yet the AI tools lag Adobe by a generation, so Generative Fill and Neural Filters are out of reach. The free tier shows ads. And since every load needs a connection, treat Photopea as an online editor that keeps your files on your device, not as an offline or self-hosted one.

Frequently asked