Read the save state
The editor reports the open edit, the library revision, backup generation, approved-folder delivery, and reopen verification separately. A library save can fail while a .pixelwall checkpoint is delivered successfully. Do not treat one Saved label as proof of all five states.
Use a verified checkpoint
Generate a project backup, save its artifact to the approved folder, verify its checksum and bytes, then reopen it with the CLI or desktop file path. The compact project preserves layers, frames, image links, palettes, and metadata. It does not preserve undo history or local recovery revisions. Browser download completion cannot be observed by PixelWall.
Open without adding to the library
Open temporary loads a project for inspection or continued work without creating a library entry. File-backed mode keeps the project tied to its approved file and saves through that file. Before closing, temporary and file-backed documents need a verified checkpoint or a successful bound-file save. PixelWall never removes unrelated projects automatically.
Measure before cleanup
The storage panel and persistence response separate the configured budget, current usage, artwork, recovery history, and available space. Remove or archive only a project you recognize, and keep a verified file checkpoint before changing library contents.