YOUR APPROVED MASTER STAYS THE MASTER
Your PSD is the template. Not a recreation.
Template editors are excellent for creating new layouts quickly. SudoMock is for teams that already have an approved Photoshop master and do not want to maintain a second version somewhere else.
Silent product demo: update wording, text styling, supported warps, and rotation while the approved PSD stays the source of truth.
One source of truth for design. Controlled values for production.
The difference is not whether another tool can import a PSD. The difference is what becomes the runtime master. SudoMock targets the live layers in the Photoshop file your team already approved.
WHEN A SECOND TEMPLATE IS REQUIRED
Maintain a second master
- 1Create or import the layout
- 2Recreate the editable fields
- 3Approve the second version
- 4Keep both versions aligned
PSD MASTER + SUDOMOCK
Automate the approved file
- 1Upload the approved PSD
- 2Target live text and artwork slots
- 3Send the final values
- 4Render controlled variations
HONEST COMPARISON
Choose SudoMock when Photoshop fidelity is the constraint.
- SudoMock fits
- Existing PSD library, controlled variation, fixed art direction
- Template editors fit
- No-code authoring, collaboration, fluid layouts, publishing
- Production check
- Test every master against the compatibility matrix
EXISTING IMPLEMENTATION GUIDES
Start with the product your PSD already represents.
The same live-layer contract applies across these ten existing guides. They stay available for specific implementation intent without defining the whole capability.
REST API + HOSTED MCP
Choose the channel that matches the workflow.
Both channels render from the PSD you own. The REST API exposes the multi-layer contract for production workflows; hosted MCP keeps one render tool narrower for assisted work inside an AI client.
| CAPABILITY | REST API | HOSTED MCP |
|---|---|---|
| Required input | REST APIAt least one entry across smart_objects, text_layers, or group_layers. | Hosted MCPmockup_uuid, smart_object_uuid, and artwork_url are required. |
| Smart Objects | REST APITarget multiple Smart Objects in one request. | Hosted MCPOne Smart Object and one artwork URL per tool call. |
| Text layers | REST APIUp to 50 overrides; each provides exactly one of text or segments. | Hosted MCPAt most one override, using text or text_segments. |
| Mixed-style text | REST API1 to 32 segments per layer, with documented per-layer and per-request limits. | Hosted MCPOne mixed-style layer per call, with the same per-layer backend limits. |
| Text-only PSD | REST APIUpload and render without a Smart Object. | Hosted MCPUpload accepts it; render_mockup cannot render it because artwork and Smart Object inputs are required. |
| Group outlines | REST APIUp to 50 group_layers overrides. | Hosted MCPAt most one group-outline override alongside the required artwork. |
| Repeated renders | REST APIOne output per request; repeat requests and use is_async to queue each render. | Hosted MCPOne output per tool call; an assistant can repeat calls, but there is no native batch tool. |
| Fonts | REST APICatalog fonts for every account; custom TTF or OTF upload and delete on Pro and Scale. | Hosted MCPBrowse and use catalog or already-uploaded fonts; no custom-font upload or delete tool. |
| Output | REST APIPNG, JPG, or WebP from 100 to 10,000 px, subject to account limits. | Hosted MCPThe same backend formats and account limits. |
Scope: PSD text personalization through POST /api/v1/renders and the hosted render_mockup tool. Other MCP tools have separate contracts. Both use the documented PSD renderer and compatibility matrix.