lucky.graphics

guides

Mockup Best Practices for Designers

Mockup best practices for presenting design work: choosing the right mockup type, matching perspective and lighting, avoiding common presentation mistakes, and licensing mockup assets properly.

Published
October 1, 2026
Updated
October 29, 2026
Topic
guides
Reading time
17 min
Review
Reviewed against the primary source

Mockup Best Practices for Designers

A good mockup answers one question a client or reviewer actually has, such as "how does this logo hold up on a storefront?", and nothing else. Pick the mockup type from that question, make physical surfaces (paper, fabric, packaging) respond to the artwork's perspective and light, keep device frames plain and current, and check every asset's license before it goes into client work.

Those four rules cover most of the craft. The rest of this guide is about where they bend: device mockups carry platform rules that forbid the very shadows and tilts that make print mockups convincing, app store screenshots are a separate deliverable with their own pixel requirements, and a mockup can never prove how a printed color will look. Each section below follows the order in which those decisions usually come up on a real project.

Start From the Question the Mockup Must Answer

Mockups fail most often because they answer the wrong question. A moody billboard scene is persuasive, but if the client's open question is whether the wordmark survives at business-card size, the billboard is noise. Before opening a mockup pack, write down the decision the viewer has to make, then choose the scene that makes that decision easy.

Decision the viewer is makingMockup that answers itWhat to showWhat to leave out
Does the logo work small and large?One print item plus one large-format sceneBusiness card at real scale, signage or vehicle at distanceLifestyle props, a dozen near-identical scenes
Does the identity hold together as a system?A flat-lay or stationery setCard, letterhead, envelope, social avatar side by sideUnrelated merchandise
Does this screen layout fit a real device?A plain device frameThe actual screen at true aspect ratioHands, desks, coffee, reflections
Will the packaging read on a shelf?A packaging render or shelf sceneFront panel at shelf distance, plus one side panelClose-ups that hide the shelf-distance problem
Is this the right product for our audience?One environmental scene from the audience's worldA context that matches the brand's real useGeneric "luxury" scenes the brand will never appear in
Will the merch print look right?An apparel mockup with fabric foldsPlacement, scale relative to the garment, ink on fabric texturePerfectly flat garments that hide distortion

The table is our working rule of thumb, not an industry standard. Its value is the right-hand column: most weak presentations fail on what they include, not on what they miss.

The Main Mockup Types

TypeWhat it isTypical use
Device framesPhone, tablet, laptop or desktop outlines around a screenApp and web UI reviews
Print mockupsBusiness cards, letterheads, posters photographed or rendered in a sceneBrand identity presentations
PackagingBoxes, bottles, pouches as 3D renders or photosProduct and packaging design
EnvironmentalSignage, storefronts, billboards, vehiclesBrand in the real world
ApparelT-shirts, hoodies, caps, tote bagsMerchandise and apparel graphics
Flat-laysItems arranged on a surface, shot from aboveIdentity systems, portfolio covers

For client work, environmental and print mockups answer "what will this look like out there?", which is usually the question that is really being asked. For UI work, a clean device frame on a neutral background keeps attention on the interface. For a portfolio, choosing one presentation style and repeating it across projects is what makes a body of work look like it came from one studio.

Physical Surfaces: Make the Artwork Belong in the Scene

The realism techniques in this section apply to physical objects: paper, fabric, packaging, signage, walls. Device frames follow different rules, covered in the next section.

Perspective follows the surface. A logo on a mug must wrap with the curve; a print on a hoodie must bend with the folds. Most quality mockup files give you a placeholder layer that you replace with your artwork, and the file's own warp or displacement setup bends it to the surface. If the file has no such setup, a flat paste across a curved surface is the single most obvious tell that the image is a composite.

Light and shadow match the scene. If the photo is lit from the left and falls into shadow on the right, the artwork must darken on the right too. A bright, flat logo dropped onto a low-key photograph looks pasted on, even when the perspective is perfect. Sample the scene's darkest and lightest areas and check that the artwork never gets brighter than the brightest part of the material it sits on.

Texture shows through. Ink on uncoated card, embroidery on a cap and a sticker on glass each look different. If the mockup's blending lets the paper grain or fabric weave show through the artwork, keep it. Solid, perfectly smooth color on a textured surface reads as a screen graphic, not a printed one.

Resolution is measured in pixels, not dpi. The artwork placed into a mockup must have at least as many pixels as the area it fills at the final output size. A "72 dpi versus 300 dpi" label says nothing about this on its own. Our guide to DPI, PPI and pixel dimensions explains why the pixel count is the number that matters.

Worked example: how big must the artwork be?

An illustration with stated inputs, so the arithmetic can be reused:

  • The presentation slide is 1920 x 1080 pixels.
  • In the mockup scene, the poster on the wall occupies a region about 600 pixels wide on that slide.
  • The deck will also be exported at double size (3840 x 2160) for a large display.

At 1x, the poster region needs at least 600 pixels of artwork width. At the 2x export it needs 1,200. Placing a 1,200-pixel-wide version of the poster covers both, and a vector or high-resolution master covers any later reuse. The common failure is the reverse: a 500-pixel screenshot of the poster stretched to fill 1,200 pixels at 2x, which blurs exactly the detail the client is meant to judge.

Where physical mockups stop being evidence

A mockup is a screen image. It cannot show how a printed color will turn out, because the scene, your monitor and the viewer's monitor are all RGB, and the press is not. A neon-bright brand green that looks perfect on a mocked-up box may be outside what the chosen print process can reproduce. When color accuracy is the question, the answer is a proof, not a mockup. The CMYK vs RGB print color guide covers what changes between the two, and the bleed, trim and safe area guide covers the edge rules a mockup will happily hide.

Edge cases on physical mockups

  • Metallic and spot finishes. Foil, metallic inks and spot varnish do not exist in an RGB image. A mockup can suggest them with a gradient or gloss layer, but label the slide "finish simulated" so nobody signs off on a shine the press will render differently.
  • Garment color. A white print on a heather gray shirt behaves differently from the same print on black, and both differ from the mockup's default white tee. Build the mockup on the garment color that will actually be ordered.
  • Die lines and folds. A box mockup shows the panels the photographer chose. If a key message sits across a fold or on the bottom panel, the mockup will hide that problem; check the flat die line separately.
  • Signage at distance. A storefront scene makes a sign look larger than it will feel from across the street. If legibility at distance is the question, scale the artwork to the real sign size and view the slide from the matching distance.
  • Placeholder dimensions. Many mockup files have a fixed placeholder canvas. If its proportions differ from your artwork, the file will stretch or crop it silently; match the proportions before placing, rather than accepting a distorted logo.

Device Frames: Plainer Is Correct

Device mockups are where most designers import habits from print mockups that the platform owners explicitly reject. Apple's App Store marketing guidelines, which Apple's Design Resources page points to for anyone using its product bezels, are the clearest example. When you show an app on Apple hardware in marketing, those guidelines say to:

  • Use Apple-provided bezels and show the latest-generation devices the app is developed for, in the devices and colors provided.
  • Use product images "as is." The modifications Apple lists include adding reflections, shadows or highlights, cropping, tilting or obstructing the image, and animating, flipping or spinning it. Promotional copy goes beside the device, not on top of it.
  • Avoid extreme angles and keep the product's color, shape, size and form accurate, with no added cases or covers.
  • Keep it legible: the guidelines set a minimum device size of 25 mm tall in print and 200 px onscreen, and ask for correct relative scale when several products appear together.
  • Show the real app: the screen displays the app as it appears when running, built on the latest OS version, never a blank screen, and with fictional account data rather than a real person's.
  • Do not fake the hardware: 3D renderings or simulations of Apple products are on the prohibited list, and a generic device must not carry Apple-specific details such as the Home button or sensor housing.

Whether a private design review falls inside Apple's rules is not something its text settles, and the Apple device frames guide sets out the licence clause by clause. The rules are good defaults anyway: a tilted phone with a glossy reflection pulls attention away from the interface. For any public marketing of an App Store app, read the current guidelines directly, because they change with each hardware generation.

Edge cases with device frames

  • Concept work for unreleased hardware. If the product will ship on a device that has no official bezel yet, show the screen without a frame, at the correct aspect ratio, rather than inventing hardware.
  • Dark mode products. If the product ships light and dark themes, show both. Our dark mode design guide covers what each theme needs to prove.
  • Web work. A browser window outline is usually enough. A laptop on a desk adds nothing the reviewer needs and shrinks the layout they are trying to read.
  • Small UI details. If the review is about type size or tap targets, show the screen at 100% on an actual phone, not in a frame scaled to fit a slide.

App Store Screenshots Are a Separate Deliverable

Teams often expect the presentation mockups to double as store screenshots. Apple's App Store Connect lists exact pixel sizes per device group, and Google Play requires screenshots to show the actual in-app experience and advises against device imagery, so a styled presentation mockup rarely fits either store as it stands.

RequirementApple App Store ConnectGoogle Play Console
How many1 to 10 per device sizeMinimum 2 across device types; up to 8 per device type
File formatJPEG or PNG, no alpha or transparencyJPEG or 24-bit PNG, no alpha
Example size1320 x 2868 portrait for the large iPhone display group; 2064 x 2752 portrait for 13-inch iPad320 px minimum, 3840 px maximum; recommended at least 1080 x 1920 portrait or 1920 x 1080 landscape for apps
Shape limitExact listed sizesLongest side no more than twice the shortest
Device framesNot addressed in the specification pageAvoid device imagery; Wear OS screenshots must not be framed
ContentListed pixel sizes per deviceMust show the actual in-app experience; no "Best", "#1", "Free" claims or "Download now" calls to action

Worked example: one capture, two stores

A team captures an iPhone screen at 1320 x 2868 for App Store Connect and plans to upload the same file to Google Play. The ratio of long side to short side is 2868 / 1320 = 2.17. Google Play's rule caps that ratio at 2.0, so the file is not valid there as it stands.

The fix is to produce the Play set from the Android build at a compliant size, for example 1080 x 1920 (ratio 1.78), using screens captured from the actual Android app. Reusing the iOS capture with letterboxing would also pass the ratio rule, but it would show iOS interface details to Android users, which defeats Google's requirement that screenshots demonstrate the "actual in-app or in-game experience". The same 2.0 check is worth running on every portrait capture from a tall phone before upload, because every Face ID and Dynamic Island size in Apple's list exceeds it, as the next section shows.

Screenshot Shapes: Apple's Full List Against Play's Two-to-One Rule

The worked example checks one file. We ran the same check on every portrait size Apple lists in its screenshot specifications, as the page read on October 29, 2026: 25 sizes across the iPhone and iPad groups. For the oldest groups, which list sizes with the status bar and without, we used the sizes with it. The number for each size is simply the long side divided by the short side.

Apple's 25 portrait screenshot sizes against Google Play's 2:1 limitRange bars of long side divided by short side for Apple's portrait screenshot sizes, grouped by device family. iPads run 1.33 to 1.52, iPhone Duo 1.42 to 1.45, the 3.5-inch iPhone 1.50 and Home Button iPhones about 1.78, all under Play's limit of 2.0. The ten Face ID and Dynamic Island sizes run 2.16 to 2.17, all over it.Play limit: 2.0iPad (9 sizes)1.33 to 1.52iPhone Duo (2)1.42 to 1.453.5-inch iPhone (1)1.50Home Button (3)1.78Face ID (5)2.16 to 2.17Dynamic Island (5)2.171.52.0long side / short side
Apple's 25 portrait screenshot sizes against Google Play's 2:1 limitEach bar spans the lowest to highest ratio in the group; the number in brackets is how many listed sizes the group has. Dashed line: Google Play's rule that the long side may be no more than twice the short side. Oldest groups use the size with status bar.Source: Apple, App Store Connect screenshot specifications, and Google Play Console Help, preview assets, both read October 29, 2026. Ratios are Lucky Graphics arithmetic on the listed pixel sizes.
Show the data as a table
Apple portrait screenshot sizes and their long-to-short ratios
Apple groupPortrait sizes (pixels)Ratio
iPhone Duo, outer display1398 x 20341.45
iPhone Duo, inner display2007 x 28531.42
iPhone with Dynamic Island, large1260 x 2736; 1290 x 2796; 1320 x 28682.17; 2.17; 2.17
iPhone with Face ID, large1284 x 2778; 1242 x 26882.16; 2.16
iPhone with Dynamic Island, medium1179 x 2556; 1206 x 26222.17; 2.17
iPhone with Face ID, medium1170 x 2532; 1125 x 2436; 1080 x 23402.16; 2.17; 2.17
iPhone with Home Button, large1242 x 22081.78
iPhone with Home Button, medium750 x 13341.78
iPhone with Home Button, 4 inch640 x 1136 (with status bar)1.78
iPhone with Home Button, 3.5 inch640 x 960 (with status bar)1.50
iPad 13 inch2064 x 2752; 2048 x 27321.33; 1.33
iPad 11 inch1488 x 2266; 1668 x 2420; 1668 x 2388; 1640 x 23601.52; 1.45; 1.43; 1.44
iPad 10.5 inch1668 x 22241.33
iPad 9.7 inch1536 x 2048; 768 x 1024 (with status bar)1.33; 1.33

Ten of the 25 sizes break Play's rule, and they are exactly the ten sizes in the four Face ID and Dynamic Island groups, all between 2.16 and 2.17. Every other size sits comfortably inside it: the Home Button iPhones at about 1.78, the 3.5-inch iPhone at 1.50, the two iPhone Duo displays at 1.42 and 1.45, and the iPads between 1.33 and 1.52. In practice, any capture from an iPhone with Face ID or Dynamic Island needs reworking before Play will accept it, while an iPad capture already meets the 2:1 rule without reshaping.

Three things are worth knowing before you plan the export:

  • Apple's required sizes. The specification page says that to submit an app you must provide at least one screenshot for "iPhone with Dynamic Island (medium display)", plus one for the iPad 13-inch display if the app supports iPadOS. Apple also lists an iPhone Duo group, with an outer display at 1398 x 2034 and an inner display at 2007 x 2853, and says that starting in April 2027, screenshots will be required for any app using the iOS 27.1 SDK or later. Those two shapes are much closer to square than the tall phones, so a layout composed for a 2.17 frame will not simply scale into them.
  • Scaling does not fix shape. Apple's page says that if your interface "is consistent across multiple device sizes and localizations, you only need to provide screenshots for the highest required resolution", and App Store Connect scales them down. Resizing keeps the proportions, so a scaled 2.17 image is still 2.17 when it reaches Play.
  • Cropping costs real content. Bringing a 1320 x 2868 capture to exactly 2:1 at full width means cutting 228 pixels of height, 7.9% of the image. Bringing it to Play's recommended 9:16 means cutting about 521 pixels, 18.2%. That is usually more than a status bar, and it often reaches the tab bar the screenshot was meant to show.

So treat the shape as a design input, not an export setting. If one set of marketing screens must serve both stores, compose the important content inside a central 9:16 area from the start, and capture each platform's version from its own build. A shape that passes is still not enough on its own: an iOS capture letterboxed into a Play frame still shows Android users an interface they will not get, which runs against Google's requirement that screenshots demonstrate the "actual in-app or in-game experience". Store icons follow the same logic of one master and per-platform exports, which our app icon sizes guide works through.

Structuring a Client Presentation

A sequence that works for both brand and UI presentations:

  1. The reveal: one image. Open with the strongest single application: the primary lockup on signage, or the hero screen in a plain frame. One image gives the room one thing to react to.
  2. The system: two or three images. Show the design across applications: card plus letterhead, or three key screens. This is where a logo becomes an identity, or a screen becomes a product.
  3. The real world: one or two images. One environmental shot from the audience's world. This is the emotional close.
  4. The details: as many flat slides as needed. Construction grids, clear space, color values, type specs. These are for handoff, so they come after the persuasion, not before it. A brand style guide is where these details live long term.

Narrate what each mockup proves as you show it ("this is the logo at 20 mm on a card"), then move on. If a slide has nothing to say, it should not be in the deck.

How many mockups is enough?

The sequence above lands between four and six mockups, plus the flat detail slides, and that range is our recommendation rather than a measured optimum. The point of a cap is that each image must earn its slot by answering a question from the first table. A deck that shows the same mark on a billboard, a mug, a T-shirt, a van and a phone case answers one question five times.

Common Mistakes and Their Fixes

MistakeWhat the viewer concludesFix
Old device framesThe work, not just the frame, is datedUse current bezels from the device maker
Tilted, glossy phones with reflectionsThe scene matters more than the interfaceStraight-on, unmodified frame; copy beside it
Floating screenshot with a drop shadowThis is a concept, not a productSeat it in a plain frame or show it unframed at true ratio
Flat artwork on curved or folded surfacesNobody thought about the real objectUse the file's warp setup or pick a flat surface
Mixed lighting moods across slidesThe identity has no centerOne scene family per presentation
Busy lifestyle props in a design reviewThe reviewer is judging the stock photoNeutral backgrounds for review; styled scenes for marketing only
Wrong context (a bank app on a beach)The designer does not know the audienceScenes from the brand's actual world
Blurry hero imageEverything else is suspect tooCheck each mockup at 100% at the export size
Light theme only for a product with dark modeHalf the product was not designedShow the themes that ship
Real customer data on screenA privacy problem, not just a design oneFictional names, numbers and photos

Licensing Mockup Files

Mockup files are licensed assets, the same as fonts and photos. Three things to check before client work:

  • Commercial and client use. Some free mockups allow personal use only, some allow commercial use with attribution, and some forbid use in client deliverables. Our free mockups for commercial use guide compares specific sources and their actual terms.
  • Redistribution. Delivering a layered PSD to a client, or putting a mockup inside a brand guidelines PDF the client will share, may count as redistribution even when using the mockup in a presentation is fine.
  • Photo and product rights. A photographic mockup inherits the photographer's license, and a scene showing a recognizable product can carry trademark rules, as the Apple guidelines above show.

Save each license page as a PDF in the project folder with the date you downloaded the file. The design asset licensing checklist covers the full record-keeping routine, and the Creative Commons licenses explainer covers what NC and ND terms mean for client work.

Mockups Earlier in the Process

Mockups are not only for the final presentation:

  • Early layout checks. Dropping a rough layout into a plain frame at true aspect ratio exposes layouts that only worked on a wide artboard.
  • Stakeholder rounds. People who struggle to judge a flat artboard often give clearer feedback on an object they recognize, so a single environmental mockup can shorten a feedback round.
  • Handoff notes. An annotated mockup showing where a pattern meets a seam, or how a label wraps a bottle, answers production questions before they reach the printer.
  • Portfolio case studies. A consistent mockup style across case studies is part of what makes the portfolio feel deliberate. Who owns the right to show client work there is a separate question, covered in our design ownership and work-for-hire guide.

Pre-Presentation Checklist

Run this on the finished deck, one mockup at a time:

  • The mockup answers a named question from the client's brief.
  • Device frames are current, unmodified and straight-on, with copy beside them.
  • Screens show the real product (or the real design), with fictional data.
  • Physical surfaces show perspective, light and texture on the artwork.
  • Artwork pixel width is at least the region's pixel width at the largest export size.
  • All mockups share one lighting mood and one realism level.
  • Both themes are shown if the product ships both.
  • Every mockup file's license allows commercial and client use, and is saved in the project folder.
  • Store screenshots are produced separately from presentation mockups, at the listed sizes.
  • Each image checked at 100% zoom on the display it will be presented on.

Frequently Asked Questions

Can I add a reflection or tilt to an iPhone mockup?

Not if the image markets an App Store app and uses Apple's product images. Apple's marketing guidelines list reflections, shadows, highlights, tilting and cropping as prohibited modifications. Apple's text neither exempts nor covers a private review (see the Apple device frames guide), but the plain version almost always shows the interface better.

Should mockups be photorealistic?

For brand and packaging presentations, usually yes, because the question is how the design will look as a real object. For interface reviews, no: a plain frame or no frame keeps the reviewer on the layout. Photorealism also raises expectations about color that a screen image cannot meet for print work.

Can I upload my presentation mockups as store screenshots?

Usually not. Apple lists exact pixel sizes per device, Google Play wants the actual in-app experience and advises against device imagery, and a tall iPhone capture can break Play's two-to-one shape rule. Plan the store set as its own export.

What resolution should artwork be before I place it in a mockup?

At least as many pixels as the area it will fill at the largest size the deck will be shown or exported. Work out the region's pixel width on the slide, multiply by the export scale, and place artwork at or above that width. Vector artwork avoids the question entirely until it is rasterized.

How do I keep portfolio mockups consistent across very different projects?

Fix three variables and let the rest change: one background tone, one lighting direction, and one camera angle family (all straight-on, or all three-quarter). Projects can then differ in content without the portfolio looking like a collage of mockup packs.

Where These Rules Come From (checked October 22, 2026)

The "decision to mockup" table, the artwork sizing example and the presentation sequence are the editorial team's own working methods, not figures from these sources. The screenshot shape ratios and crop amounts are our arithmetic on Apple's listed pixel sizes.

Mockups usually end up inside a slide deck, so the natural next read is our guide to presentation templates you can use in paid client work: it checks which deck templates are cleared for commercial use, so the frame around your mockups is as safe to deliver as the mockups themselves. More guides are collected on the learn hub.