Picture the brief for your next developer-tool demo. Engineers hate marketing, someone says. So show the code, go dark and skip the narrator. Now look at 49 real ones. Most do the opposite. A narrator talks, the words stay plain, and code gets one short moment. So before you brief a technical demo on code alone, look at what carries the rest.
A developer-tool demo shows a product sold to engineers, like an API, a database or a coding agent. Its code environment is where engineers write and run code: an editor or a terminal. ADVIDS Research studied 49 of these videos from 43 companies, including Anthropic, GitLab, Microsoft and OpenAI. The report sees only the screen and the script. Whether a choice wins your engineering buyers is yours to test.
Seven patterns stand out. Videos record the real product (Live Capture). Code shows up once, early (Code Moment). A narrator explains it (Voice Track). Scripts talk to you (Direct Address). The words stay plain (Plain Words). Most stop by 1:30 (Tight Cut). And the code's background is picked apart from the video's (Two Grounds).
ADVIDS Research · 49 developer-tool videos · 43 companies · 42 scripts · 13 coded frame by frame · published 14 September 2026 · 17 min read
Top takeaways
Live Capture
8 of the 13 videos coded frame by frame record the real product, and 4 use an animated interface instead.
Code Moment
8 of the 13 show code on screen, and the typical one shows it by 0:09.
Voice Track
86% of the 49 videos use a voiceover, and just 7 run on music alone.
Direct Address
69% of developer-tool scripts say 'you' at least twice in every 100 words.
Plain Words
64% of scripts use fewer than 3 developer words in every 100.
Tight Cut
67% of developer-tool demo videos run 1:30 or less.
Two Grounds
59% of the videos use a light or mixed background, though code itself mostly sits on dark.
Questions this report answers
How do developer tool demo videos show code in 2026?
As one short moment, early. That's the Code Moment. Of the 13 videos coded frame by frame, 8 put code on screen. In a typical one, code first shows up at 0:09. Anthropic and OpenAI make 4 of those 8. Pinecone and Cequence Security show no code at all, just diagrams or forms.
Should a developer tool video use a screen recording or an animated mockup?
Record it, if your engineer will use that screen. That's Live Capture. Of the 13 videos coded frame by frame, 7 use a screen recording alone and 3 use a drawn mockup alone. Anthropic records Claude Code as it runs. LangChain draws LangSmith, because it suggests changes no live account shows on cue.
Do developer tool videos use dark mode?
The code does. The video often doesn't. That's Two Grounds. 59% of the 49 videos use a light or mixed background, and 41% use dark. But when code is on screen, it sits on dark in 5 of 6 videos. GitLab's dark code sits inside a lighter video.
Do developer tool demo videos use a voiceover?
Mostly. That's the Voice Track. 86% of the 49 videos use a voiceover (42 of 49). The 7 on music alone include all four Anthropic and OpenAI videos. Music works there because a typed request on screen does the talking. If your screen can't explain itself, use a narrator.
How technical should a developer tool video script be?
Plainer than most briefs assume. That's Plain Words. 64% of the 42 scripts use fewer than 3 developer words in every 100, like API, SDK or deploy. The typical script uses just 3 different ones. Microsoft Agent Framework runs far higher, because the open-source projects it joins are the news.
How long is a developer tool demo video?
Most stop at 1:30. That's the Tight Cut. 67% of the 49 explainer and demo videos run 1:30 or less, and the typical one runs 1:13. Only 8 run past 2:00. OpenAI's Codex video runs 0:46. Superblocks takes 2:25, because each control it sells needs its own screen.
How was this analysis done?
ADVIDS Research screened 945 videos against a rule written before the work began. 49 qualified, from 43 companies selling developer tools. Each script was counted, and 13 videos were coded frame by frame. The seven patterns, Live Capture, Code Moment, Voice Track, Direct Address, Plain Words, Tight Cut and Two Grounds, are simple counts.
How to read this report
This report looks at 49 developer-tool demo and explainer videos from 43 companies, uploaded 2 January 2024 to 3 August 2026. Each figure counts videos, and patterns 4 and 5 count the 42 with a script. Patterns 1 and 2 use just the 13 coded frame by frame, so read them as hints.
Pattern 01 · Live Capture
1. Most videos record the real product instead of drawing it.
Most developer-tool videos show the product as it really runs. Of the 13 videos coded frame by frame, 8 use a screen recording. Only 4 use a drawn copy of the screen. So if your engineer will use the screen you're showing, record it. Draw only the screen no live account can show.
Think of an open house. The floor plan helps, but buyers walk the real rooms. Your terminal and your code diff are the rooms.
Most videos pick one way. 7 use a screencast of the product alone, and 3 use an animated product UI alone. Only ScienceLogic mixes the two. So the product reaches the screen as a real recording far more often.
Example: Anthropic's Claude Code desktop app video runs 0:37 on music. At 0:16 you see a real code diff, green and red lines on a dark background. Nothing is redrawn.
Videos that record the product: companies in this group include Anthropic, Airia, Akto, Cequence Security, etc.
Exception: a product that suggests code changes. LangChain's LangSmith Engine video draws its screens, including a proposed code change and a Merge button. No live account shows that on cue, so a drawing does the job.
Source: Advids analysis of the 13 coded frame by frame
Videos pick one way. Only ScienceLogic uses both.
Pattern 02 · Code Moment
2. Code shows up once, early, then the product takes over.
Most videos put code on screen, but only for a moment. Of the 13 videos coded frame by frame, 8 show code, and it comes early. If your engineer types into your product, show one line they would type. If they don't, skip the code and show the result.
A chef shows the knife once. Then the dish. Your import line or API call is the knife.
Code reaches the screen as a terminal, a typed line or a recorded code environment. Anthropic and OpenAI make 4 of those 8 videos. Some also add moving text or a diagram around the code.
Example: GitLab's video opens on code being typed. By 0:04, two Python lines sit on a violet background: import sys, and from pathlib import Path. One line, then the product.
Code on screen: companies in this group include Anthropic, GitLab, LangChain, OpenAI, etc.
Exception: setup with no code. Cequence Security's AI Gateway video shows forms and dashboards, one after another. It promises setup without custom code, so the forms are the demo.
Source: Advids analysis of the 13 coded frame by frame
Pattern 03 · Voice Track
3. A narrator explains the product in most videos.
Engineers may hate marketing, but they still get a narrator. 86% of these videos use a voiceover (42 of 49). The code shows what the product does. The voice says why it matters. So if your screen can't explain the product with the sound off, write for a narrator.
Think of a museum audio guide. The painting can't tell you what's behind it. Your architecture diagram is the painting.
Developer tools get explained out loud, even database architecture. Voiced videos also run longer: 1:16 is typical, against 0:46 on music alone.
Example: Pinecone's How Pinecone Works video runs 2:27 over diagrams. At 0:48 a dark grid lays out the API, Log Writer, Index Builder and Query Router. The voice explains what no screen could.
Videos with a voiceover: companies in this group include Microsoft, Tricentis, Acurast, Pinecone, etc.
Exception: a typed request does the talking. OpenAI's Codex video runs 0:46 on music. A chat asks Codex to build a page for a summit, so the words are already on screen.
Source: Advids analysis of 49 developer-tool videos
Pattern 04 · Direct Address
4. Most scripts talk to you, not about the company.
Most scripts talk straight to the engineer. 69% say 'you' at least twice in every 100 words (29 of 42). Few lean on 'we' or 'our'. And few call the viewer a developer by name. So if your script talks about your company, turn each line toward the engineer.
A good doctor says 'your knee', not 'the patient's knee'. Your engineer hears the same gap between 'we ship' and 'you ship'.
'You' beats 'we' in 34 of the 42 scripts. Only 31% name developers or engineers at all (13 of 42).
Example: HPE's OpsRamp video says 'you' more than 5 times in every 100 words. At 1:07, one word fills the screen: Proactive.
Scripts that say 'you' often: companies in this group include Amazon Web Services, Atlantic.Net, Cube, HPE, etc.
Exception: buyers who already run your stack. SUSE's Choice Happens spot never says 'you'. It lists the Linux and Kubernetes tools SUSE builds, because its buyers already run them.
Source: Advids analysis of 42 developer-tool scripts
Pattern 05 · Plain Words
5. Scripts use few developer words, even for technical products.
The products are technical. The scripts mostly aren't. 64% use fewer than 3 developer words in every 100 (27 of 42). Developer words are terms like API, SDK, deploy or query. So keep the names your engineer must recognize. Let the screen show the rest.
A street sign names one street. It doesn't print the whole map.
An API word shows up in 18 scripts. Just 2 name a programming language or git. Most sell developer tools with few developer words.
Example: Akto sells API security with almost no developer words in its script. At 1:03 the screen does the technical talking. It lists ten policies, like rotating API keys every 30 days.
Scripts with few developer words: companies in this group include Akto, CyberArk, Deepgram, Domino Data Lab, etc.
Exception: when the names are the news. Microsoft's Agent Framework video names Semantic Kernel, AutoGen, MCP and A2A. It joins two open-source projects, so their names are the story.
Source: Advids analysis of 42 developer-tool scripts
Pattern 06 · Tight Cut
6. Most videos stop at 1:30 or sooner.
Most developer-tool videos are short. 67% run 1:30 or less (33 of 49). That's enough time for one request and one result. So if a step is setup, move it to a separate walkthrough. Keep the demo for the moment your product does its job.
A test drive goes around the block. Nobody gets the keys for a road trip. Setup is the road trip.
A typical developer-tool demo here runs 1:13. Only 8 run past 2:00.
Example: OpenAI's Codex video runs 0:46. At 0:09, one request sits on screen: build a page for an upcoming summit. The agent replies that it checks the workspace first.
Videos of 1:30 or less: companies in this group include Dremio, F5, Forethought, OpenAI, etc.
Exception: every control needs proof. Superblocks 3.0 takes 2:25. It builds an app, sets up a database, scans packages and deploys, because each control it sells needs its own screen.
Source: Advids analysis of 49 developer-tool videos
The typical video runs 1:13. Only 8 run past 2:00.
Pattern 07 · Two Grounds
7. The code sits on dark, but the video often doesn't.
You might expect developer videos to go dark. Most don't. 59% use a light or mixed background (29 of 49). Yet when code is on screen, it almost always sits on dark. So treat the editor's theme and the video's background as two separate choices.
Think of a laptop in dark mode on a bright desk. Nobody repaints the desk to match.
Of the 6 videos whose frames show code, 5 put it on dark. And 3 of those sit inside a lighter video, GitLab among them.
Example: LangChain goes the other way. At 0:31 in its LangSmith Engine video, a code panel sits on white, with a Save button. Light code in a light video.
Light or mixed videos: companies in this group include BrowserStack, CData, GitLab, LangChain, etc.
Exception: no code to show. Pinecone's How Pinecone Works video stays dark all the way, with magenta and violet diagrams. When the product is infrastructure nobody sees, the diagram is the screen.
Source: Advids analysis of 49 developer-tool videos
Neither light nor dark holds half. Each video picks its own.
Benchmarks
Check your own software demo video against these typical figures.
Length, sound, script and screen
| Measure | Typical | What it means |
|---|---|---|
| Length | 1:13 | Half the 49 videos run shorter |
| Talking time | 84% | Share of the video with someone speaking |
| Words in the script | 150 | Spoken words, across the 42 scripts |
| Developer words in every 100 | 2.6 | Words like API, SDK, deploy or query |
| Different developer words | 3 | In one script |
| 'You' in every 100 words | 2.9 | You, your, you're and the like |
| 'We' in every 100 words | 0 | We, our, us |
| Time code is on screen | 16% | Share of the video, in the 8 that show code |
| First code on screen | 0:09 | Time into the video, in the 8 that show code |
A typical video runs 1:13, talks most of the way and shows code by 0:09.
What fewer than half do
| Pattern | Videos | Out of |
|---|---|---|
| A developer word near the start of the script | 20 | 42 |
| Dark background | 20 | 49 |
| A readable line of code on screen | 5 | 13 |
| Code on screen for over a quarter of the video | 3 | 8 |
| Moving text in the same video as code | 3 | 8 |
None of these reaches half, and no video coded frame by frame puts a presenter on camera.
Seven questions for your next demo brief
Answer these seven in writing before anyone books the edit.
- Pattern 01 Will your engineer use the screen you're showing? Record it, using a demo repository and account fit to show.
- Pattern 02 Does your engineer type into the product? Put one line they would type on screen by 0:09.
- Pattern 03 Can the screen explain the product with the sound off? If not, write for a narrator and budget the voice early.
- Pattern 04 Does your script say 'you' more than 'we'? If not, rewrite it so the engineer is the subject.
- Pattern 05 Does every developer word earn its place? Stay under 3 in every 100, unless the names are the news.
- Pattern 06 Is any step setup? Cut the demo to 1:30 and move setup to a separate walkthrough.
- Pattern 07 Were the editor theme and the video background picked apart? If not, decide each on its own.
Now go back to that brief: show the code, go dark, skip the narrator. Here it fits only Anthropic's terminal videos. They keep code up longest, on music alone. Their product is the terminal. Is yours?
This week, mute your last demo. Mark every second code is on screen. Then answer the seven questions on one page.
Most briefs ask how much code to show. These videos show it once, then explain it.
Methodology
| Product category | Videos |
|---|---|
| Data platforms, databases and pipelines | 12 |
| Model, agent and LLM-application platforms | 11 |
| Build, test and deploy (DevOps, CI/CD, testing) | 7 |
| AI coding and app-building tools | 5 |
| Application, API and ML security | 5 |
| APIs, gateways and integration | 4 |
| Cloud, compute and infrastructure | 3 |
| Observability and IT operations | 2 |
| Coding scheme | Values | Definition |
|---|---|---|
| Product category | 8 categories | Judged at screening from title, description and script; the base for engineering buyers. All {n}. |
| Sound | voiceover · music only · speech share | From audio analysis. Speech share is the share of runtime with detected speech. All {n}. |
| Script address | you per 100 words · we per 100 words · names developers or engineers | Counted on caption tracks of 15 words or more. {n_scripts} scripts. |
| Developer terms | per 100 words · distinct terms · first 15 percent of words | Every match of the fixed lexicon listed in the methodology. {n_scripts} scripts. |
| Runtime | seconds | Read from the file. All {n}. |
| Frame | light · dark · mixed · brightness 0 to 255 | Computed: mean luminance across nine sampled frames, title cards and diagrams included. Not the editor theme. All {n}. |
| Build | screen_recording · ui_mockup · 2d_animation · 3d_cgi · kinetic_type | Coded from frames, with a confidence of high or medium. {n_visual} visually coded videos. |
| Code on screen | terminal segment · confirmed code text · screen-capture segment | Coded per timed segment; code text matched by pattern and confirmed by reading; share of runtime is the union of code segments. {n_visual} videos. |
| Code ground | dark · light · both | Coded by eye on frames cut at the midpoint of each code segment. {n_ground} videos whose frames show code. |
| Not coded | cast · surface · altitude · build on the other rows | The {not_visual} videos without a visual record carry no frame coding, and this report does not code them from scripts. |
Cite this report
Jai Ghosh, Advids. 49 Developer-First Demo Videos Analyzed: How to Visually Present Code Environments for Engineering Buyers. 14 September 2026. https://advids.co/blog/developer-tool-demo-videos-code-on-screen
About Advids
Advids produces video for AI, SaaS and DeepTech companies. ADVIDS Research publishes coded studies of what those companies ship, with the dataset attached so every count can be checked.