Blog › Device Mockups for SaaS and App Landing Pages
How to make device mockups for a SaaS or app landing page that load fast and look sharp
By Nguyễn Thành Dân, Founder of Drint ·
A good device mockup for a landing page starts with a screenshot at the device's exact pixel size, such as 1320 × 2868 px for a 6.9-inch iPhone. Export the picture at twice its display width, serve it as WebP or AVIF, and keep it under Google's 2.5-second LCP target. This guide uses web.dev and MDN pages read on 18 November 2026.
Why it matters: on most SaaS and app sites, the device picture in the hero is the largest element on the screen. That makes it the element Google times for Largest Contentful Paint. A beautiful mockup that loads late costs you twice: in search and in sign-ups.
Key points
- Use the screenshot size the device expects; a mismatched capture is stretched or cropped.
- On a display with a device pixel ratio (DPR) of 2, an image needs twice its CSS width in pixels to look sharp, according to web.dev.
- Lossy WebP is on average 25–35% smaller than JPEG, and lossy AVIF around 50% smaller, according to MDN.
- A "good" LCP is 2.5 seconds or less at the 75th percentile of page loads, web.dev says. Never lazy-load the hero image.
- Every mockup needs real alt text that says what the screen shows, not "image of phone."
Which devices and angles should a landing page use?
Start from your users, not from the newest phone. A B2B dashboard is mostly used on laptops, so the hero should be a laptop or monitor. A consumer app lives on phones, so lead with a phone and show the tablet layout lower down.
| Product | Hero device | Feature sections | Why |
|---|---|---|---|
| B2B SaaS dashboard | Laptop or 24-inch monitor | Phone for the mobile companion | Buyers judge the main working screen first |
| Consumer iOS app | Current iPhone | iPad, Apple Watch | Matches the App Store set the visitor saw |
| Android-first app | Galaxy or Pixel phone | Tablet in landscape | Avoids an iPhone on an Android product |
| Cross-platform app | One iPhone and one Android phone | Laptop for web app | Shows both stores without crowding |
Angle follows purpose. A straight, front-on device reads best when the visitor must read the UI, such as a pricing table or a chart. A turned, three-quarter device adds depth and suits a hero, where the shape of the product matters more than every label.
Limit a hero to one or two devices. Each extra device shrinks every screen, and small UI text turns into grey noise on a phone.
How do I match the screenshot to the device?
Each device screen has a fixed pixel grid. Capture at that grid, or the mockup tool must stretch or crop your picture.
| Device (Drisp page) | Screen | Screenshot size |
|---|---|---|
| iPhone 17 Pro Max | 6.9-inch | 1320 × 2868 px |
| iPhone 17 | 6.3-inch | 1206 × 2622 px |
| Samsung Galaxy S25 Ultra | 6.9-inch | 1440 × 3120 px |
| iPad Pro 13-inch (M5) | 13-inch | 2064 × 2752 px |
| MacBook Neo | 13-inch, open | 2408 × 1506 px |
| 24-inch monitor | 24-inch | 1920 × 1080 px |
Sizes are from Drisp's device pages, read on 18 November 2026. The iPhone sizes match Apple's App Store screenshot classes; our guide to App Store and Google Play screenshot sizes lists every one.
For a web app on a laptop, size the browser so the page content fills the device's screen grid. A page viewport of 1204 × 753 CSS pixels on a display with a device pixel ratio of 2 renders at 2408 × 1506 device pixels. That is the MacBook Neo grid on Drisp.
The sum is CSS pixels × devicePixelRatio. MDN defines that property as the ratio of physical pixels to CSS pixels, and says "a value of 2 is expected for HiDPI/Retina displays." Check the value in your browser's console with window.devicePixelRatio before you capture.
How sharp does the exported mockup need to be?
Screens on most phones and laptops pack two or three physical pixels into each CSS pixel. That ratio is the device pixel ratio, or DPR.
web.dev's image course gives the rule with an example. An 800-pixel image shown in a 400-pixel layout slot has "double the pixel density." On a DPR 2 display it looks crisp; at 400 px it would look soft.
Worked example: a 560 px hero
Say the hero device sits in a column 560 CSS px wide.
| Screen | DPR | Pixels needed |
|---|---|---|
| Older laptop or monitor | 1 | 560 px |
| Retina laptop, most phones | 2 | 1,120 px |
| Phones at 3× | 3 | 1,680 px |
A 1,024 px export covers this slot only at DPR 1. A 2,048 px export covers it at 2× and 3×. For feature sections at 320 CSS px wide, 1,024 px is enough even at 3×.
Do not send the 2,048 px file to everyone. web.dev cites data shared by Matt Hobbs: about 18% of GOV.UK browsing sessions in November 2022 reported a DPR of 1. Those visitors pay for pixels they cannot see.
Use srcset so the browser picks. MDN describes the x descriptor: 2x marks a file "to be used when the pixel density is double the standard density."
``html <img src="hero-1x.webp" srcset="hero-1x.webp 1x, hero-2x.webp 2x" width="560" height="560" alt="Invoice dashboard on a laptop, showing paid and overdue totals" fetchpriority="high"> ``
How should light and shadow work?
Light is what turns a flat frame into an object. Three rules hold in most heroes.
- One light direction. If the device's highlight comes from the top left, its shadow falls to the bottom right. Two devices lit from different sides look pasted together.
- A soft contact shadow. A thin, dark shadow where the device meets the ground anchors it. Without it, the device floats.
- Glass that reflects, but not over the UI. A faint highlight across the screen says "glass." A bright streak over a button hides the thing you are selling.
Match the background to your page. A mockup on studio grey dropped onto a white page shows a visible box. Export on white for a white page, or on a transparent background to sit on any colour.
Which file format and size should the mockup be?
MDN's image format guide, last modified 5 November 2026, gives these averages.
| Format | Typical saving | Transparency | Notes from MDN |
|---|---|---|---|
| Lossy WebP | 25–35% smaller than JPEG | Yes | Broad support in current browsers |
| Lossless WebP | About 26% smaller than PNG | Yes | Good for UI with flat colour |
| Lossy AVIF | Around 50% smaller than JPEG | Yes | No progressive rendering; add a fallback |
| PNG | Baseline | Yes | Use for exact, lossless copies |
| JPEG | Baseline | No | Widest support |
MDN recommends a fallback when using AVIF, through the <picture> element:
``html <picture> <source type="image/avif" srcset="hero-2x.avif 2x, hero-1x.avif 1x"> <img src="hero-1x.webp" srcset="hero-2x.webp 2x" width="560" height="560" alt="…" fetchpriority="high"> </picture> ``
Download the mockup as PNG, then convert it. Converting once, from the lossless master, avoids stacking compression artefacts.
Hero image or feature-section image?
| Hero | Feature section | |
|---|---|---|
| Role | Usually the LCP element | Below the fold |
| Loading | Never loading="lazy"; add fetchpriority="high" | loading="lazy" is fine |
| Export | 2× the slot width, 2,048 px for wide slots | 1,024 px for slots up to about 340 CSS px at 3× |
| Devices | One or two | One per feature |
| Background | Matches the page, or transparent | Same as hero for consistency |
How do device mockups affect Core Web Vitals?
Largest Contentful Paint (LCP)
web.dev counts <img> elements as LCP candidates. Its LCP page, last updated 4 September 2025, sets the target: 2.5 seconds or less for at least 75% of page loads.
web.dev's "Optimize LCP" guide, last updated 31 March 2025, splits LCP into four parts. On a well-tuned page, time to first byte and image download take about 40% each. The two "delay" parts, load delay and render delay, should each stay under 10%.
The same guide warns: "Never lazy-load your LCP image." It suggests fetchpriority="high" on the likely LCP image, but on no more than one or two images. In a web.dev test on Google Flights, a high fetch priority on the hero background cut LCP from 2.6 s to 1.9 s.
A smaller file alone may not help. web.dev shows a case where a lighter image only shifted time into render delay, because JavaScript hid the hero until it loaded. Render the hero in the HTML, not after a script runs.
Cumulative Layout Shift (CLS)
A good CLS score is 0.1 or less; above 0.25 is poor, according to web.dev. A mockup without width and height loads at zero height, then pushes the text down.
MDN says width and height let the browser compute the aspect ratio "prior to the image being loaded" and reserve the space. Set them on every mockup.
How do I write alt text for a device mockup?
The phone is not the content; the screen is. Describe what the screen shows and why it is there.
| Weak alt | Better alt |
|---|---|
| "image of iPhone mockup" | "Habit tracker home screen on an iPhone, showing a 12-day streak" |
| "laptop.png" | "Invoice dashboard on a laptop, with paid and overdue totals" |
| "" on a hero | Alt that names the product and the screen |
| Long feature list | One sentence; put details in the caption or body |
MDN says alt text "should not describe the presence of the image itself or the file name." An empty alt="" tells screen readers the image is decoration. Use it only when the picture adds nothing the text does not already say.
What are the most common device mockup mistakes?
- A stretched screenshot. A 1080 × 1920 px capture forced into a 1320 × 2868 px screen is squeezed by about 18% in one direction. Round icons turn into ovals. Capture at the device's size, or let the tool crop from the centre.
- The wrong status bar. An Android status bar on an iPhone, a carrier name, a low battery or a 3:07 a.m. clock all read as careless. Clean the bar before capture.
- An out-of-date device. A home-button phone on a 2026 landing page dates the product. Use a current model unless you sell to users of old devices.
- Moiré from downscaling. Fine stripes, grids or small text can shimmer in waves when a large image is shrunk. Export near the final display size and avoid many-step resizing.
- Text too small to read. If the visitor must read a number, crop to that part of the UI or use a larger device.
- A lazy-loaded hero. It delays the LCP element by design, web.dev warns.
- No size attributes. The page jumps when the image arrives, which raises CLS.
What can Drisp do that a flat frame cannot?
Drisp is Drint's device-screen tool, live at drint.io/drisp. It draws each device as a 3D model with Drint's own render engine, the same one behind Drint's packaging mockups. It is not a screenshot pasted on a photo.
On 18 November 2026, the Drisp catalogue listed 102 devices: 50 phones, 2 foldables, 24 tablets, 23 watches, 2 laptops and 1 monitor. Brands include Apple, Samsung, Google, Xiaomi, OPPO, OnePlus and vivo, plus generic devices without a maker's logo.
| Drisp feature | What you get |
|---|---|
| True-size bodies | Modelled from published drawings, e.g. iPhone 17 Pro Max at 77.98 × 163.43 × 8.75 mm |
| Exact screen grid | Each page shows the size to capture; other sizes are cropped from the centre, never stretched |
| Frame finish | Original, black / silver, champagne gold, midnight blue |
| Background | Studio grey, white or transparent PNG |
| Motion | Gentle swing, push in, rise, full spin or still, from your screen recording |
| Export | Free up to 1,024 px with a light grid; Drisp Pro clean up to 2,048 px |
| AI editors | The Drisp MCP server returns the PNG from Claude, Cursor or ChatGPT |
The centre crop matters for mistake number one. Drisp fills the screen edge to edge and crops rather than squashes, so a wrong-sized capture loses an edge, not its proportions.
The foldable pages, such as iPhone Duo, show both screens. Watches range from the Apple Watch Ultra 4 at 422 × 514 px down to older series. Drisp's MCP server works the same way as Drint's packaging one, described in our post on Drint MCP in ChatGPT and Claude.
What this means for designers
Treat the device mockup as a performance asset, not decoration. Decide the slot width first, then export at 2× that width. Convert the PNG to WebP or AVIF, and set width, height and alt text before you hand it to the developer.
Keep one master capture per screen at the device's exact size. The same file feeds the App Store set, the landing page hero and the launch post. Only the frame, background and crop change.
Check the hero after launch in a lab tool and in field data. web.dev's 75th-percentile target means one fast test on office Wi-Fi does not prove the page is fast for most visitors.
Sources
- web.dev, Largest Contentful Paint (LCP), last updated 4 September 2025, accessed 18 November 2026.
- web.dev, Optimize Largest Contentful Paint, last updated 31 March 2025, accessed 18 November 2026.
- web.dev, Optimizing resource loading with the Fetch Priority API, last updated 14 November 2023, accessed 18 November 2026.
- web.dev, Cumulative Layout Shift (CLS), last updated 12 April 2023, accessed 18 November 2026.
- web.dev, Learn Images, Descriptive syntaxes, last updated 1 February 2023, accessed 18 November 2026.
- web.dev, Learn Images, WebP and AVIF, last updated 1 February 2023, accessed 18 November 2026.
- MDN Web Docs, Window: devicePixelRatio property, last modified 13 November 2026, accessed 18 November 2026.
- MDN Web Docs, Image file type and format guide, last modified 5 November 2026, accessed 18 November 2026.
- MDN Web Docs, The Image Embed element: img, last modified 11 September 2026, accessed 18 November 2026.
- Drint, Drisp device catalogue and device pages linked above, read 18 November 2026.
Try it
Open the Drisp laptop list or phone list, pick the device your users carry, and drop in a screenshot at the size the page shows. Download the PNG on a transparent background, convert it to WebP or AVIF, and it is ready for your hero.
Frequently asked questions
What resolution should a device mockup be for a website?
Twice the width it is displayed at, for 2× screens. A device shown 560 CSS px wide needs about 1,120 px; serve a 1× file too with srcset.
Is WebP or AVIF better for mockups?
AVIF is usually smaller, around 50% below JPEG versus 25–35% for WebP, according to MDN. AVIF does not render progressively, so keep a WebP or PNG fallback.
Should I lazy-load the hero mockup?
No. web.dev says never to lazy-load the LCP image. Lazy-load mockups further down the page instead.
Why does my screenshot look stretched on the device?
Its proportions differ from the screen. Capture at the device's exact size, such as 1320 × 2868 px for an iPhone 17 Pro Max.
What alt text should a phone mockup have?
Describe the screen, not the phone: what the app shows and why it matters, in one sentence.
Can I use a transparent background?
Yes on a website. Drisp exports transparent PNGs. App Store screenshots, however, must not contain transparency.