Pixel art in the service workspace
Pixel Art Studio opens inside a service rather than as a standalone editor, and the assets it produces stay connected to the rest of the workspace. That affects how you handle exports, versions, and milestones.
Service context
Section titled “Service context”In Lunar Paper, the brief, the asset, the publishing record, the people with access, and the surrounding documents and pages all sit in one service. When you publish a version of a pixel art project, that milestone exists in the same place as everything else the work depends on.
Connections
Section titled “Connections”Finished pixel art usually ends up in one of these places:
- Asset Library for centralised storage and reuse across the service.
- Documents for briefs, style guides, and technical specs that reference the art.
- Pages for showcases, review hubs, and internal galleries.
- Publishing for release records, public URLs, and version handoff.
- Brand Hub when pixel art is part of a brand system (icons, in-product marks).
- Team and Content Access for permissions over who can view or edit the project.
These links exist automatically because the project and its neighbours share the service. You do not have to wire anything up or copy files between places.
Publish Version
Section titled “Publish Version”The Publish button in the editor records a versioned milestone with a comment. Use a published version as the handoff point, because it sits in the service where a reviewer, an importer, or a teammate can point at it. Use meaningful comments (silhouette_approved, palette_locked, walk_cycle_timing_ready, export_ready, final_v1) rather than v2 or update.
The full mechanics of auto-saves, published versions, restore, and rollback are in Version history and publishing.
Team access
Section titled “Team access”The service controls who can reach the module and its projects through Content Access and team membership. If someone outside the immediate team needs to review a pixel art project, publish a version and point them at the service. That is usually cleaner than exporting a file and sending it through chat.
Direct exports
Section titled “Direct exports”For quick edits that need only a PNG, export directly. Working inside a service gives you linked assets, versions, and permissions when you want them, and it does not get in the way of a simple export. See Quickstart for a plain PNG export.