The product slide: using mockups to present your interface clearly

Short answer: The product slide is often the first time your audience sees the interface. Show it on a suitable device, use a quiet on-brand background, keep the screen easy to read, and export it at the size your deck needs. Repeat the same visual system across product slides so the presentation feels coherent.

Every pitch has a moment where you show the product. Up to that point, you may have been describing a problem, an audience, or a proposed solution. The product slide connects that story to the interface itself.

The interface still needs to be legible, and the presentation around it should support rather than compete with it. A device mockup can provide useful context, particularly when the hardware matters to how the product is used.

Why the product slide carries so much weight

The product slide has to explain what the interface is, where it runs, and which part deserves attention. A mockup, your screen shown inside a device model, can answer the first two questions without adding another paragraph of copy.

There is a practical reason to keep it clear too. A deck may be skimmed later, forwarded without your narration, or reopened after the meeting. The product slide should still make sense on its own.

Match the device to the story

The device you choose sets the frame for the whole pitch. Pick the one that matches who you're building for:

• Consumer mobile app? A phone gives the interface its expected context.
• Business or web product? A laptop or large display gives a wider interface enough room to stay legible. Our guide to SaaS launch visuals covers this use case in more detail.
• Both mobile and desktop? Show both only when the product genuinely supports both experiences.

Whatever you pick, make sure the device supports the story instead of becoming the story. If you're new to mockups, our introduction to device mockups covers the basics.

Here's a simple way to decide:

If your product is…	Lead with…	What it provides
A consumer mobile app	A phone	Familiar mobile context
A SaaS or B2B tool	A laptop	Space for a wider interface
A pro or technical platform	A large display	Room for dense controls and data
A cross-platform product	The devices it actually supports	A direct view of each experience

Keep the background quiet

The background's job is to support the screen without competing with it. Two approaches are reliable starting points:

• Your brand colour, solid. Pull your primary colour, set it behind the device, and every product slide now matches the rest of the deck.
• A soft gradient. Gentle and out of the way, it adds a little depth without pulling focus.

Whichever you choose, carry the same palette and lighting across the product slides. You can vary the composition while keeping the deck visually connected.

Use focus to guide the eye

A soft blur behind the device can separate it from the background and direct attention towards the screen. This effect, called depth of field, works best when the interface remains crisp and the blur is restrained.

On a slide that may only be seen briefly, a clear visual hierarchy matters more than decorative detail. We cover how to use the effect without overdoing it in our depth-of-field guide.

Consider adding motion

For a pitch delivered live or shared as a video, a still can become a short, quiet clip: the device easing into frame or the camera moving between two useful views. Motion can show a change or direct attention, but it should still serve the point of the slide.

Keep it restrained. One smooth move is often enough; anything busier can distract from what you're saying. If you want to try it, turning one screenshot into a launch video walks through the approach.

Export for each placement

Pitch visuals often reappear in a data room, on a website, or in a follow-up email. Keep a high-resolution master, then crop or re-export it for each placement so the device stays large enough to read.

Two practical tips:

• Match the export to the slide. Use the deck's aspect ratio and enough resolution for the display or projector you expect to use.
• Use a transparent background when you need flexible placement. Ultramock includes transparent PNG and WebP exports on Pro. Transparency is supported in Chrome; results in other browsers can vary.

A worked example: three product slides

Imagine a fictional personal finance app. Here is one way the principles could come together across three product slides, so the sequence feels connected rather than assembled from unrelated images.

The introduction slide, after you've framed the problem. A single phone, held straight on, shows the app's main dashboard on a brand-blue background, with a soft blur behind it. One short headline sits beside it: "Your whole financial life, in one place." Nothing else.

The detail slide, a few slides later, goes deeper on the core feature. The same phone, background, and angle now show the spending breakdown, with the caption "See exactly where your money goes." Keeping the surrounding treatment consistent makes the change in screen content easy to follow.

The range slide, near the close, shows the experiences the product actually supports. The phone sits beside a laptop on the same blue background and under the same light. A short label can make the message explicit: "Desktop and mobile." Matching the background and lighting helps the two devices belong in one composition.

The thread through all three is restraint and consistency. The background, palette, and lighting stay connected while the screen and composition change with the story.

Common mistakes on the product slide

• Screenshots without enough context or contrast. The interface becomes harder to place or read.
• A different background on every product slide. Breaks the sense of a designed deck.
• Too much on the screen. Show the one view that proves the value, not the whole app.
• A tiny device lost in empty space. Let the product be the hero of the slide.
• Low-resolution images. They fall apart the moment the deck hits a projector.

Frequently asked questions

Do I really need mockups, or will screenshots do? Screenshots can be the better choice when interface detail is the point. A device mockup is useful when hardware context, composition, or brand presentation matters. Many decks benefit from using both at different moments.

Which slide should the product first appear on? It depends on the story. Some decks lead with the product; others establish the problem first. Put the first product view where it answers the audience's next question rather than following a fixed slide number.

Should every product slide use the same device and background? Use a consistent visual system, but not necessarily the exact same composition. Keep the palette, lighting, and device treatment related while changing the view when the content requires it.

How large should I export the images? Export for the deck's dimensions and expected display size. Starting with a larger master gives you more room to crop, but check the final slide at presentation size to make sure the interface remains sharp and legible.

Can I use these mockups on my website and in emails too? Yes. Reuse the visual system, then adapt the crop, scale, and aspect ratio for each placement rather than forcing one export into every format.

Putting it together

Choose a device that matches the product, set a quiet on-brand background, keep the interface legible, and export for the slide. Repeat the visual system where it helps the audience follow the story.

If you would rather not build the composition by hand, Ultramock's 3D app mockup maker includes device models, backgrounds, camera controls, depth of field, and image or video export. The core editor is free; Pro adds premium devices, higher-resolution and watermark-free exports, transparent PNG and WebP output, and more export formats.