FAQ
Questions, answered without marketing
If something here is unclear, the contact page goes to a human. Everything below describes how the editor actually behaves.
Files and privacy
Are my images uploaded to a server?
No. The editor is a WebAssembly application that runs inside your browser tab. Files are opened, edited and written locally; there is no upload endpoint at all. You can verify it in the network panel: after the application has loaded, opening a file produces no network requests.
What happens to my files when I close the tab?
They are discarded, unless you exported them. Nothing is written to cloud storage and there is no autosave to a server. Export before closing if you want to keep the result.
Is there a file size limit?
The limit is the memory available to the browser tab, not a policy. Documents of a few thousand pixels per side with dozens of layers are comfortable; extremely large documents will be slow or fail to open on low-memory machines.
Can I use it offline?
After the application has loaded once, the browser cache keeps it available. The editor itself does not require a network connection to process files.
Formats and compatibility
Which formats can it open?
PSD and PSB documents with layers, plus PNG, JPEG and WebP images. Layered PSDs open with their layer stack, groups, masks and blend modes.
Can it save back to PSD?
Yes. Documents can be written back as PSD with layers intact, which is what makes quick fixes possible without flattening the file.
Why does a text layer look different from the original?
The font referenced by the layer is probably not installed on your system, so a fallback is substituted and line breaks shift. The text stays editable; install the font to get the original metrics back.
Are smart objects supported?
Smart objects render at their stored resolution and can be moved, scaled and exported. Editing the original document inside a smart object is not supported.
Does it support CMYK or 16-bit documents?
No. It is an RGB editor for screen output. CMYK conversion and soft proofing belong to colour-managed desktop software.
Browsers and hardware
Which browsers work?
Chromium-based browsers with WebGPU enabled: Chrome and Edge 113 or newer. Safari and Firefox support for WebGPU is still catching up, so the editor may not start there yet.
How do I check whether WebGPU is available?
Open chrome://gpu and look for WebGPU in the feature list, or run `navigator.gpu` in the console — a defined object means the API is present. Some corporate browser policies disable it; in that case the editor cannot start regardless of hardware.
Do I need a dedicated graphics card?
No. Integrated graphics with WebGPU support handle typical documents well. Dedicated graphics matter for very large canvases and heavy layer stacks.
Why does the first load take so long?
The application itself is about 14 MB of WebAssembly, downloaded once and then served from cache. Subsequent visits start in about a second.
The site itself
Is PhotoPSD free?
Yes. No account, no trial timer, no watermark on exports. The site is funded by advertising rather than subscriptions.
Is this Adobe Photoshop?
No. PhotoPSD is an independent project built on the open-source PhotoCraft editor. It is not affiliated with, endorsed by or sponsored by Adobe Inc.
Where does the source come from?
The editor is built from PhotoCraft, dual-licensed MIT / Apache-2.0. The site publishes its attribution and licence files, and links to the upstream repository from the footer.
Still stuck?
Send a description of what you expected and what happened. Bugs with a reproducible file get priority.
Contact usFaster than reading: just try it. Open the editor →