Search documentation
Find setup, feature, and troubleshooting guides.
- Documentation
- Image generation
Image generation
Generate and edit images in Studio, keep the results with your project, and continue the workflow on desktop or mobile.
Start in Studio
Image generation is a Studio node, not a separate settings workflow. Your project, inputs, outputs, and edits stay together in the vault.
- Open Studio from the command palette or Settings → SystemSculpt → Studio.
- Create a project with New Studio project. New projects use
SystemSculpt/Studiounless you change the projects folder in settings. - Add an Image Generation node to the project.
- Enter a prompt, choose an image model and its output options, then run the node or the whole project.
Configure the Image Generation node
Credits and estimates
The picker’s credit estimates include the SystemSculpt service fee. The final charge uses actual generation cost with the fee and credit conversion accepted when the job started, rounded up to whole credits. Reference images and prompt processing can add cost. A conservative temporary hold can exceed the estimate; unused credits are released after settlement. If billing cannot be verified, the hold remains for reconciliation and the result is withheld. Refreshing or reconnecting to the same job does not generate or charge it twice.
Run and review
Run the image node from its action bar, or run the active project from the command palette. Studio shows a pending output while generation is in progress. Each completed output becomes an image media card connected to the generation node.
The workflow is stored as a .systemsculpt project. Its generated and edited media live in the matching .systemsculpt-assets folder beside it.
Image cards keep the useful actions close to the result: Edit with AI, Edit image, Copy image, Replace media, and Delete node.
Choose the right editing path
The local editor also lets you adjust text styling and layer order. Its Fit action recenters the canvas without changing the saved image.
Desktop and mobile
Some local-machine nodes still require desktop Obsidian: CLI, dataset, audio extraction, and terminal. Mobile hides unavailable nodes and blocks a run before it starts when the project includes one.
Reveal in Finder is also desktop-only. Keep cross-device projects to portable nodes when you need to run them from a phone or tablet.