Screen Dressing · Journal · 4 min read
Why You Shouldn't Put Real Software on Camera (Clearance, Logos & the DP)
Pointing a camera at a real desktop feels like the path of least resistance — the software's already there, it's free, it works. Then your software clearance for film turns into a headache, the brand you photographed says no, and your DP quietly hates every flickering frame. This piece explains the legal and technical reasons crews avoid real software on camera, and why a neutral, fictional UI sidesteps the whole problem.
(Quick disclaimer: this is practical production guidance, not legal advice. For a specific project, talk to your production lawyer or clearance house.)
The clearance and logo problem
Most recognisable software is wrapped in trademarks: a logo, a distinctive interface, a product name. Putting that on screen can mean using someone's brand in your film without permission, and what's "fine" versus "a problem" is rarely obvious from the outside.
Productions take this seriously for a few reasons:
- Trademark and brand risk. A brand owner can object to how their mark appears — especially if your story casts the product in a bad light (the email service used by the villain, the bank that ruins a family).
- Implied endorsement. A clearly featured product can read as a paid placement or an endorsement that doesn't exist, which cuts both ways legally.
- Distribution gatekeepers. Broadcasters, streamers, and insurers (via errors-and-omissions cover) often require a cleared "fill-in" list. Unexplained logos in frame can hold up delivery.
Why brands say no
Even when you ask nicely, the answer is often no — and the reason is usually the script. Brands have no upside in being the product on screen during a hack, a fraud, a breakup, or a meltdown. Their approval process is slow, legalistic, and built to protect the brand, not your shoot schedule. "We'll just get permission" can burn weeks and still end in a rejection, after which you're back to re-shooting or covering it in post anyway.
The DP's technical objections
Clearance aside, your director of photography has separate, entirely valid reasons to dread a real screen in shot:
| Issue | What it does on camera |
|---|---|
| Refresh / shutter mismatch | Rolling dark bands or flicker scrolling through the frame |
| Moiré | Shimmering interference patterns where the sensor and pixel grid fight |
| Brightness | Screens blow out to pure white or force the rest of the frame into shadow |
| Colour temperature | Screens read very blue and clash with the lighting and grade |
| Live unpredictability | Real notifications, wrong clock, spinning beachballs mid-take |
Each of these costs takes on set or money in post. A real OS adds the worst one — unpredictability. A pop-up notification, an auto-update, a low-battery warning, or simply the wrong time in the corner can ruin an otherwise perfect take, and you won't always catch it until the edit.
Why a neutral fictional UI sidesteps all of it
A purpose-built fake interface solves the legal and the technical problems in one move. There's no real brand, so there's nothing to clear. The content is invented, so it can be as dramatic as the story needs — declined, breached, leaked, melting down — without a brand-approval committee. And because a good prop is built for camera, it's designed to be readable, controllable, and steady under the lens.
Crucially, a fictional UI can still be obviously the kind of thing your audience recognises without being any specific product:
- A Bloomberg-style financial trading desk reads as "high-finance terminal" without naming a real one.
- A corporate webmail inbox gives you the email scene without a real provider's logo in frame.
- A generic social media feed lets a character doomscroll without putting a real platform on trial.
- A generic search-engine results page covers the "look it up" beat without showing the real one.
Each is a self-contained web page: no install, no network calls, no logos, runs full-screen on any monitor. You control the content, so the screen says exactly what the scene needs and nothing it shouldn't.
A simple decision rule
When a script puts software on screen, ask three questions:
- Is a recognisable brand visible? If yes, you're now in clearance territory — assume slow and uncertain.
- Does the story put that brand in a bad light? If yes, expect a no.
- Can a fictional stand-in do the same dramatic job? Almost always, yes.
If the honest answers are "brand visible, story unflattering, fiction works fine," the call makes itself: use a neutral prop.
Clear the frame, keep the schedule
Real software on camera trades a few minutes saved now for clearance risk, brand approvals, and a frustrated DP later. A neutral fictional UI gives you a screen that's legally clean, technically steady, and says precisely what your scene needs — with nothing to clear and nothing to fix in post.
Browse the catalogue of fictional screen props, or request a custom build and a quote if your scene needs a screen that doesn't exist yet. Then read how films and TV fake computer screens for the bigger picture.
Need a screen for your scene?
Every prop is free to open and runs full-screen in any browser. Browse the full catalogue, or tell us what your scene needs and we'll build it.