A PSD that looks fine in Photoshop can render wrong, slowly, or not at all everywhere else. If you build templates you intend to reuse — or run through any automated tool — a handful of structural decisions determine whether they work reliably.
This is the specification worth following.
Layer structure
One Smart Object, at the top level. Not nested inside groups, not inside another Smart Object. Automated tools locate the placeholder by scanning top-level layers; anything buried three groups deep is a coin flip.
Name it something a machine can find. Good conventions, in rough order of how widely they're recognised:
artwork
design
input
placeholder
smart objectAvoid Layer 12, Rectangle 1 copy 3, or PUT YOUR DESIGN HERE!!! — the first two carry no information, the third is fine for humans and unpredictable for tools.
Keep the layer stack shallow. A working template needs roughly this:
├── highlights (Screen or Overlay, above artwork)
├── shadows (Multiply, above artwork)
├── artwork ← the Smart Object
└── background (the base photograph)Four to eight layers. If your template has forty, most are doing nothing and each one costs render time.
Delete hidden layers. Photoshop keeps hidden layers in the file; some renderers evaluate them anyway. They inflate file size and occasionally appear in output where you didn't expect them.
Canvas size and resolution
Long edge: 2000–3000 px. Etsy displays listing images up to 3000px and recommends at least 2000px on the shortest side for zoom to work well. Above 3000px you're adding render time and file size for no visible gain.
Aspect ratio: square where possible. Etsy's thumbnails are square, and non-square images get centre-cropped in the grid. Building templates square means what you compose is what buyers see. Full detail in Etsy image size requirements.
Document resolution: 72 DPI is fine. DPI is metadata for print; for screen output only the pixel dimensions matter. Setting 300 DPI on a screen-destined mockup quadruples file size and changes nothing visible. This is different for the artwork inside the Smart Object if you also print it — see print resolution and DPI.
Colour profile and bit depth
sRGB, always, for mockups. Adobe RGB and ProPhoto have wider gamuts, but browsers assume sRGB. A mockup exported in Adobe RGB looks desaturated and slightly shifted in every browser, and it's a common cause of "my colours look wrong on Etsy."
Convert with Edit → Convert to Profile → sRGB IEC61966-2.1. Not Assign Profile — Convert.
8 bits per channel. 16-bit doubles file size and offers nothing for a JPEG destined for a listing page. Image → Mode → 8 Bits/Channel.
The Smart Object's embedded document
Easy to get wrong, because it's out of sight.
Match the aspect ratio to your artwork. If you sell 2:3 posters, the embedded canvas should be 2:3. A square embedded canvas means every design needs repositioning after placement — trivial once, painful across a hundred renders.
Size it generously. The embedded canvas sets the sharpness ceiling. If the Smart Object appears 1400px wide in the final mockup, the embedded document should be at least that, and comfortably more if the artwork is ever scaled up within the scene.
Leave it empty or use a neutral placeholder. A grey rectangle or faint grid. Don't leave a previous design in there — it ships with the file and confuses anyone (or anything) replacing it.
Effects that don't travel well
Some Photoshop features render correctly only in Photoshop:
- Layer styles on the Smart Object itself (drop shadow, bevel) — often ignored by other renderers. Bake shadows into their own pixel layers instead.
- Adjustment layers with clipping masks — usually work, occasionally reorder. Test before relying on them.
- Smart Filters — applied filters on Smart Objects are Photoshop-specific. The Displace filter in particular may not survive; if a texture matters, consider a baked texture overlay layer as well.
- Blend If sliders — advanced blending options are frequently dropped.
- Text layers with unusual fonts — the font won't exist on a rendering server. Rasterise any text that's part of the template.
Rule of thumb: pixels travel, instructions sometimes don't. If an effect matters visually, it's safer as a rasterised layer than as a live effect.
File size and render time
A well-built mockup PSD lands somewhere between 20MB and 120MB. Above that, check for:
- Multiple full-resolution copies of the base photograph
- A 16-bit document that should be 8-bit
- Hidden layers left in from the build process
- An embedded Smart Object holding a 6000px design when 2000px suffices
- Maximise Compatibility enabled — it stores a flattened composite alongside the layers. Useful for third-party tools that can't parse layers; wasteful if nothing needs it. File → Preferences → File Handling.
Render time scales roughly with layer count and canvas area. A 40-layer 6000px template takes several times longer than an 8-layer 2500px one, per design, on every render.
A validation pass before you trust a template
Before adding a template to your permanent library:
- Double-click the Smart Object — does it open a proper editable canvas?
- Drop in a bright, obviously-wrong test image (a red grid works well). Save. Does it appear correctly warped, with scene lighting applied?
- Does the test image sit behind the shadow and highlight layers, not on top of them?
- Export a JPEG at 2000px. Open it. Is it sharp at 100%?
- Check colour: does the exported file look the same in a browser as in Photoshop? If not, you have a profile problem.
- Run it through whatever bulk tool you use with one design, before committing a catalogue to it.
Templates that pass all six are safe to build a workflow on. Templates that fail step 3 are the most common problem in downloaded files — the artwork placed above the lighting layers looks flat and fake regardless of how good the underlying photo is.
Why the structure pays off
A properly-specified template is the difference between a library you can render a hundred designs through unattended, and one that needs a human to check each output.
Once every template in your library follows the same convention — one top-level Smart Object named artwork, sRGB, 8-bit, 2500px square, lighting layers above — a bulk renderer like PSDmate can process your entire catalogue in one pass without surprises. The setup work is one afternoon; the payoff is every render after that.
Template specification:
| Property | Value |
|---|---|
| Smart Objects | Exactly one, top level, named artwork |
| Canvas | 2000–3000 px, square where possible |
| Colour profile | sRGB (converted, not assigned) |
| Bit depth | 8 bits/channel |
| Layer count | Under 10 |
| Lighting | Separate Multiply + Screen layers above the Smart Object |
| Effects | Rasterised, not live |
| Embedded canvas | Matches artwork aspect ratio, generously sized |
Frequently asked questions
How should I name layers in a mockup PSD?
Name the replaceable slot something an automated tool will recognise — Magic, Design, Your Design or Artwork all sit at the top of the priority list most renderers use. Name the product body layer unambiguously too, so it is not mistaken for the artwork slot.
What colour profile should a mockup PSD use?
sRGB, 8-bit. It is what web tools, browsers and Etsy all assume, and anything else invites a colour shift somewhere in the chain. 16-bit doubles file size and render time for no benefit in a mockup.
Do layer effects survive in web-based mockup tools?
Mostly, but not universally. Complex layer styles, some blend modes and adjustment layers with unusual settings are the ones that translate imperfectly. Test a template once through the tool that will use it rather than assuming.
What canvas size should a mockup template be?
Large enough that the output clears Etsy 2000 pixel minimum comfortably — 3000 pixels or more on the short edge is a sensible floor. Much beyond 5000 buys nothing visible and costs render time on every single job.
Why does my PSD render slowly?
Usually pixel count, layer count and nested smart objects, in that order. Flattening the parts of the file that never change and removing hidden layers you are not using is the cheapest speed-up available.