# PSD Import

> Bring a layered Photoshop design in as components — and send it back out.

Glider documentation · Building Graphics · Web page: https://cgglider.com/docs/psd-import/

Sections of this page: [Importing](https://cgglider.com/docs/psd-import.md) · [Layer mapping](https://cgglider.com/docs/psd-import/layers.md) · [Round trip](https://cgglider.com/docs/psd-import/roundtrip.md) · [Cleanup](https://cgglider.com/docs/psd-import/cleanup.md)

What happens to a .psd.

PSD in the Inspector palette uploads the file, parses it in the browser, and turns its layer tree into editor groups and nodes.

1. The .psd is posted to the page's psd/ folder.
2. It is parsed and its layer tree walked.
3. Each Photoshop group becomes a Glider group; each text layer becomes a text node; each raster layer becomes an image node with its own PNG uploaded beside the .psd.
4. A manifest JSON is written next to the file, recording every layer's path, bounds, opacity and hidden state.
5. The new nodes and groups are spliced into the scene, with the root group selected.

| Limit | Value |
| --- | --- |
| Max file size | 1 GB |
| Max layers | 300 |
| Max group depth | 4 — deeper groups are flattened into their parent |

Flattening is non-fatal: the import reports how many group shells were dropped, and their contents survive in the parent group.

![A PSD imported as groups and nodes.](https://cgglider.com/docs-shots/psd-import.png)