Frequently Asked Questions

SudoMock accepts PSD and PSB files (Adobe Photoshop). API uploads support files up to Adobe's official PSD file size limit; dashboard uploads are capped at 300MB. Each file must contain at least one smart object layer, and that is the layer the API replaces with your design artwork.

A standard render costs 1 credit. A 2D Mockups render costs 5 credits. Management operations such as listing mockups, fetching details, updating metadata, or deleting are free and do not consume credits.

Smart objects are special Photoshop layers that act as design placeholders. When you call the render endpoint, the API replaces each smart object with your artwork image, applying the layer's warp, perspective, blend mode, and mask. Every PSD must have at least one smart object layer for the render to work.

It depends on the layer type. A hidden smart object is not exposed as a slot and is not rendered: to use it, make the layer visible in Photoshop and upload the file again. SudoMock flags any hidden smart objects on upload, so you know which layers to enable. A hidden text layer works differently. It is kept as a fillable slot and renders only when you add your own wording, staying hidden when you leave it empty. Nothing in your source file is changed.

Treat every artwork URL as immutable: it must always point to the same image. To change a design, upload it to a NEW URL and render with that. Reusing one URL for different content is not supported and can return the earlier image. This most often affects Google Drive: 'Replace file' and 'Manage versions' keep the SAME link, so the link keeps resolving to the original design. Upload the new design as a NEW file, which gets its own link, and render with that link instead.

Yes. You can send multiple render requests simultaneously. Your plan determines the concurrency limit: Starter allows 3 parallel renders, Pro allows 10, and Scale allows 25. Requests beyond the limit are queued and processed as capacity becomes available.

SudoMock outputs PNG, JPG, and WebP. WebP is the default because it produces the smallest files with no visible quality loss. You can configure the format via the export_options.image_format field in your render request. Maximum output dimension is 10,000 px on either side.

Use smart object layers for every design area you want the API to replace. Set the document color mode to RGB. Resolution between 72 and 300 DPI works well. Flatten complex layer effects that do not need to stay live. See the PSD Preparation guide in the docs for a full checklist and common pitfalls.

2D Mockups automatically turns a product photo into a reusable mockup, then renders any design onto it through the API without a PSD template. You can review and adjust the prepared result in the dashboard. Each render costs 5 credits.

You pay a monthly subscription that includes a bundle of credits. Unused credits do not roll over to the next billing period. If you need extra capacity, pay-as-you-go top-up packs are available at any time. Plans start at $25 per month.

Yes. Sign up with your email and you receive 500 one-time API credits. No credit card is required to create an account or make your first renders.

All 27 Photoshop blend modes are supported, including Normal, Multiply, Screen, Overlay, Soft Light, Hard Light, Color Dodge, Color Burn, Difference, Exclusion, Hue, Saturation, Color, and Luminosity. Blend modes are read directly from the PSD layer and applied during compositing, so the output matches Photoshop exactly.

Install the SudoMock app or plugin from the respective marketplace, then connect it from your SudoMock dashboard under Integrations. Once connected, Studio sessions let your customers customize mockups directly on your storefront before adding to cart.

Use Studio, the embeddable editor. Your server makes one create-session call, you drop the returned token into a single iframe, and your customers customize the mockup on your own page. There is no render backend to build. Studio works for both PSD templates and 2D product photo mockups. It is white-label: set your logo, accent color, button text, header copy, light or dark theme, and hide optional controls through the config. Required setup controls remain governed by the session. The token is opaque and origin-bound, so a leaked token cannot be embedded elsewhere. See the Studio page in the API Reference for the full setup, the postMessage event contract, and the white-label configuration keys.

MCP stands for Model Context Protocol, a standard that lets AI assistants call external tools directly. The SudoMock MCP server is hosted at mcp.sudomock.com. Connect to it from Claude, Cursor, VS Code, or any MCP-compatible client using OAuth or your API key. Once connected, the AI assistant can upload PSDs, trigger renders, and fetch results without you writing any code.

Yes. Linked Smart Objects, placeholders that point to an external file such as @artwork.psb or zREF.psb instead of embedding the content, are supported. They render as artwork placeholders using their placement geometry, so you no longer need to embed them before uploading. In the rare case a linked Smart Object has no usable placement geometry, the upload returns a 422 with error code LINKED_SMART_OBJECT_CONTENT_MISSING. That error is permanent: fix it by choosing Embed Linked in Photoshop or by supplying the design in your render request. Retrying the same file will not help.

Yes. Set export_options.dpi (72-2400, for example 300) and SudoMock stamps a print resolution tag into the output file metadata (JPG, PNG, and WebP all carry it). The dpi tag does not change the pixels: the actual pixel dimensions come from image_size. So size your output for print using image_size = print_inches x dpi (for example, a 12 inch print at 300 DPI is 3600 px). The dpi field is opt-in and defaults to none for web mockups.