Show both, and show the flat file first. A contextual mockup answers a question a flat file cannot, which is what the design looks like in the situation it was made for. But it also introduces a specific risk that most advice on the subject skips: a client can approve the scene instead of the artwork. Flat first, context second, and never context alone. That order is not a stylistic preference. It is what keeps the approval attached to the thing you are actually delivering.
What a Mockup Is For, Stated Narrowly
A mockup places the design in the situation it will be used in: a logo on a storefront, a label on a bottle, a layout on a phone, a poster on a wall. Its job is to answer questions that a flat rectangle on a white background genuinely cannot answer. Does the mark still read at the size it will actually appear? Does the type survive a curved surface? Does the layout hold up when there is a photograph behind it?
That is the whole of it. A mockup is a test, and its value is in what it might reveal. Once you treat it that way, most of the decisions about when to use one and how to build it answer themselves.
The trouble is that the same technique is very good at something else, which is making work look expensive. That second use is where the risk lives.
The Mockup That Tests Versus the Mockup That Flatters
Two mockups can present the same logo and do opposite things to a project.
| Tests the design | Flatters the design | |
|---|---|---|
| Size shown | The smallest real use case | Large, comfortable, generous |
| Color | Includes the one-color and reversed versions | The full-color version only |
| Surface | Busy, imperfect, realistic | Clean, premium, soft lighting |
| What it reveals | Whether the design survives real conditions | Whether the scene is attractive |
| Effect on the client | Confidence based on evidence | Expectations set above the deliverable |
The flattering version is not dishonest by intent, and it is standard practice across a lot of the industry. The problem is what it does to the conversation later. A client who approved a mark rendered in soft light on dark walnut has formed an impression of the design that the actual deliverable may not match, because the actual deliverable is a set of files, and one of those files is a single-color version that will end up on an invoice in black and white. When they see that version, the disappointment is real and it feels to them like the design changed.
That disappointment turns into a revision round, and it is a revision round you effectively created during the presentation.
The useful discipline is to include at least one unflattering context. If the mark has to work small and in one color, show it small and in one color, alongside the version you are proud of. This costs you a little presentation polish and buys you an approval that will hold.
When Flat Is Not Enough
Some deliverables genuinely cannot be judged flat, and for those a mockup is not optional.
- Anything with a fold, curve, or seam. Packaging, labels, folded print, apparel. The flat artboard does not show where the design crosses a physical boundary.
- Anything judged at distance or in motion. Signage, vehicle graphics, exhibition graphics. Scale relative to a human being is the whole question.
- Anything material. Where the substrate changes the result, including embroidery, foil, embossing, and printing on colored stock.
- Anything that shares space it does not control. A banner that will sit inside somebody else's page, an ad unit, a social asset that appears in a crowded feed.
And some deliverables are usually fine flat: most documents, most reports, most digital screens seen at their native size. Adding a mockup there is a presentation choice, not a necessity, and if it makes the work look better than it is, it is a bad choice.
The Approval Trap
Here is the failure mode in one sentence: the client approves the photograph, not the file.
It happens because a rendered scene is easier to react to than an artboard. It contains lighting, texture, and often a lifestyle implication, and all of those are doing persuasive work that has nothing to do with your design decisions. The client says yes to the whole composite impression. Then delivery arrives, and the composite impression is not in the package, because what is in the package is the artwork.
Three habits prevent it.
Lead with the flat file and give it the room. The convention used by at least one large design marketplace in its own submission rules is to put the flat design first and give it roughly two thirds of the presentation space, with mockups secondary. That ratio is a reasonable default for any presentation, not just a contest entry.
Caption what is decorative. One line under the scene: "Context render, for scale only. The delivered files are the artwork above." It reads as professional rather than defensive, and it moves the approval back onto the artwork.
Name the decision you are asking for. This is the same discipline that governs the presentation as a whole, and how to present design work without losing the room covers the sequence. If the ask is "approve this mark," say that, so that nobody thinks they are approving a storefront.
A Short Pre-Send Check
Before a mockup goes to a client, four questions.
- What does this mockup test? If the answer is "nothing, it just looks good," it is decoration. Decoration is allowed, but it should not be doing the persuading.
- Is the hardest real condition represented anywhere in this presentation? Smallest size, one color, worst background. If not, add it.
- Could the client believe the scene is part of the deliverable? If yes, caption it.
- Does the flat file lead? If the first thing they see is a render, reorder it.
That check also interacts with how many directions are in the room. If you are showing several concepts, mocking up every one multiplies the work and, more importantly, multiplies what the client thinks they are choosing between. The reasoning on how many design concepts to present applies here: each mocked-up concept is another surface to comment on.
After the Presentation
Whatever you showed, the next step is the same. You need feedback that is specific enough to act on, and feedback on a mockup has a particular way of going vague, because the client is reacting to a composite and cannot always tell which part of it they are responding to. When someone says the render feels flat, they may mean the artwork, the lighting, or the surface, and those are three different problems with three different owners.
Asking in a way that separates them is a skill of its own, covered in how to ask clients for design feedback. And the whole sequence, from brief through presentation to handover, is laid out in the solo design project process if the question is where this stage sits relative to everything else.
FAQ
Should you show clients mockups or flat files?
Both, with the flat file first and given most of the space. The flat file is what you are delivering. The mockup shows how it behaves in context. Showing context alone risks the client approving the scene rather than the artwork.
Are design mockups necessary?
They are necessary for anything with a fold, curve, or material property, anything judged at distance, and anything that shares space it does not control. For most documents and screen work seen at native size they are optional, and they are a bad idea if they make the work look better than the delivered file will.
Can mockups be misleading?
Yes. A scene with generous size, soft lighting, and an expensive surface can set expectations that the delivered artwork does not meet, especially the one-color and small-size versions. Including at least one unflattering context prevents that.
How do you present a logo in context without over-promising?
Show the flat mark first, then include the hardest real conditions alongside any attractive render: smallest usable size, one color, and a reversed version. Caption the decorative scenes as context only.
What should a mockup caption say?
That the render is context for scale and that the delivered files are the artwork shown separately. One line is enough, and it moves the approval back onto the deliverable.