Text-Based Video Editing

Three Things “Edit Video with Words” Can Mean

Search results often collapse three different products into one phrase. The practical test is what your text controls and whether the system is changing uploaded footage or inventing new footage.

How the Mapping Actually Works

The whole workflow rests on one data structure: a two-way index between positions in a text document and time ranges in a media file. Everything else is interface. Four stages build and use it.

1. Transcribe with per-word timing

A transcript alone is not enough — a subtitle file gives you a sentence per cue, and a sentence is far too coarse to cut with. What the workflow needs is word-level timestamps: a start and end for each individual word. Speech models produce or align these on a coarse grid. The Whisper architecture, for example, computes a log-mel spectrogram over a 25 ms window every 10 ms — 100 frames per second — and a stride-2 convolution halves that to 50 encoder positions per second, so the native resolution is 20 ms. Any timestamp printed finer than that is arithmetic, not measurement.

2. Bind text offsets to source time

The editor holds the transcript as a list of word records, each carrying its character span in the document and its time span in the source. That gives you both directions for free: a text selection resolves to a time range, and a playhead position resolves to a word to highlight. The document you are reading is a view of a timed index, not a file in its own right.

words: [
  { "text": "we",      "start": 12.437, "end": 12.556 },
  { "text": "shipped", "start": 12.556, "end": 12.921 },
  { "text": "it",      "start": 12.921, "end": 13.024 },
  { "text": "on",      "start": 13.024, "end": 13.160 },   <- gap of 352 ms follows
  { "text": "Friday",  "start": 13.512, "end": 14.005 }
]

Two details in that snippet decide the quality of every edit made from it. Inside the phrase, each word's end is exactly the next word's start — not out of confidence, but because continuous speech has no silence between "shipped" and "it" to measure. And the 352 ms before "Friday" belongs to neither word: it is a breath, and it is the most useful number on the page, because that is where a cut can hide.

3. Resolve a deletion into surviving ranges

Deleting text does not delete anything. It marks words as dropped, and the editor recomputes the keep list: the ordered set of source spans that survive. Delete "it on" above and the program becomes [0 → 12.921] + [13.512 → end]. Note that the second range starts at 13.512 rather than 13.160 in an editor that includes the following silence. Edge policies vary: another editor may preserve the gap or offer pause controls separately. The preview decides whether that technically valid range sounds natural.

The edges also have to be snapped. Cutting inside a word truncates a phoneme: a word-final /t/ or /k/ is a silent closure followed by a release burst, and cutting between the two ends the word on a hole that reads as a swallowed syllable. A fricative like /s/ runs 100–150 ms and clips into an obvious hiss. No crossfade repairs this, because the information was never in the range you kept. So every edge moves outward to the nearest word boundary before anything is recorded.

4. Conform the picture at render

Conceptually, the surviving ranges become an edit decision list or equivalent native sequence edits. The original media remains unchanged, although an application may encode proxies or preview caches while you work. At export, picture time is quantised to whole frames: an edge at 12.921 s becomes frame 388 at 30 fps, or 12.933 s. Audio can retain finer timing, so the application must keep the linked edit coherent across both streams.

One consequence is worth stating plainly, because it explains why professional systems anchor decisions in source time rather than output time. Deleting a sentence at minute 3 shifts every subsequent moment in the finished video earlier. If a caption, a zoom or a music cue had been stored at "output second 400", it now points at the wrong content. Stored against the source, it still points at the same words.

The Lineage: Research, Descript, Everyone Else

The idea is much older than the product that popularised it. Human-computer interaction researchers had working transcript-driven video editors more than two decades ago. Carnegie Mellon's Silver paper (2002) described synchronized storyboard, editable-transcript, and timeline views. Content-Based Tools for Editing Audio Stories (UIST 2013) propagated transcript edits to speech, and QuickCut (UIST 2016) applied the interaction to narrated video. The common insight was simple: speech is easier to search and select as words than as a waveform.

Descript's current script editor made the document itself the primary commercial editing surface: delete a word and the linked media disappears; cut and paste a sentence and the media moves; restore removed media and the edit returns. That product-level inversion, not transcription alone, is what made the workflow feel new.

Other editors expose the transcript alongside a conventional project. Premiere Pro Text-Based Editing can select, cut, and rearrange transcript text while trimming and placing the matching clips on the timeline. DaVinci Resolve Studio, VEED, and CapCut now offer related transcript workflows, but their operations and restrictions are not interchangeable.

A separate research branch deserves a name because it is routinely confused with this one. Text-Based Editing of Talking-Head Video (Fried et al., SIGGRAPH 2019) let a user type a word the speaker never said and synthesised the face and mouth to match. That is generative video, not an index into a recording. Editing a transcript to remove what was said and editing a transcript to fabricate what was not are opposite operations that happen to share an interface.

Which Editors Support Text-Based Video Editing in 2026?

These are current, documented implementations as of August 24, 2026. “Text-based” does not promise the same controls in every product, so the last column matters more than the label.

Valmera belongs in the adjacent prompt-based category: it uses a word-timed transcript as one evidence layer, but the user describes the result instead of manually deleting the document. See the Valmera versus Descript comparison when choosing between delegation and direct transcript control.

Where It Runs Out

A transcript is a lossy projection of a video. Speech at a conversational 120–150 words per minute is a few hundred bits a second of information; the picture is orders of magnitude more. Anything that did not survive the projection cannot be addressed by the transcript alone. Five constraints follow. A product can overcome them by adding a timeline, frame analysis, or an editing agent, but not by pretending the missing visual and acoustic information exists inside the words.

Why It Matters in Practice

Take a 90-minute webinar that has to become a short highlight cut. Video is serial: at normal speed, reviewing every answer costs the recording's full duration. A transcript is randomly addressable. You can skim, search for a product name, jump between speakers, and read the context around a hit without scrubbing a waveform. That change in navigation is the workflow's durable value.

So you select the keepers, delete the rest, and the 11 minutes exist in about an hour. Then you watch it. The picture jumps at all forty joins, because you cut a locked-off shot forty times. Two of your keepers came from opposite ends of the session and splice a confident answer onto a tired one. The segment you moved earlier now references a slide the viewer has not seen. None of these are transcription errors. They are the parts of the edit that were never in the text, arriving all at once at the moment you thought you were finished.

The honest summary of the workflow is that it collapses the selection problem and leaves the construction problem largely intact. Deciding what survives gets faster; making the surviving passages feel like one intentional video still requires visual and audio judgment.

Common Misconceptions

How This Works in Valmera

Valmera is an agentic video editor, and it takes the index from text-based editing without taking the interface. Every upload is analysed once into a word-timed transcript with word-level timings, plus silence detection, shot detection and labelled frame tiles the agent reads directly. Every later edit resolves against that index; all cuts snap to word boundaries; transcript search resolves a phrase to a real source range rather than a scrubbed guess.

The difference is who operates it. In a transcript-deletion editor you select the words to remove. In Valmera you state the outcome — "cut the dead air and every um, then punch in when I say the price" — and the agent performs it, renders a preview, and looks at the frames it produced. That covers the two limits above that hurt most in practice: an instruction scales the same whether the recording is four minutes or two hours, and it can express how as well as what, because zooms, grades, music and framing are tools the agent holds rather than characters in a document. Decisions are written to an edit decision list in source seconds, so a cut early in the video never invalidates a caption or a zoom placed after it, and the final render always comes from the original file at source quality.

The honest limits. Valmera has no document view whose deletions cut the footage — if what you want is to delete words in a transcript by hand, Descript is the tool built for that, and our side-by-side says so. Valmera's transcript panel is editable for corrections only: fix a misheard name and the captions re-render. Captions are burned into the video, with no SRT or VTT import or export. English is the best-tested transcription path. And the timings are model estimates carrying the boundary error described above — when a cut lands a beat late, the fix is to say so and have it moved, not to assume the number was ground truth.

Sources and Review Method

Product behavior was checked against first-party documentation on August 24, 2026. Historical and technical claims use the original research papers rather than affiliate roundups. Feature access can vary by plan, platform, language, and staged rollout, so follow the linked product documentation before choosing a workflow.

• Descript — Edit like a doc — Current script-editing behavior, media-linked deletion and reordering, and non-destructive restore.
• Adobe — Text-Based Editing overview — Premiere's current transcript-to-timeline workflow, filler-word tools, supported languages, and limitations.
• Blackmagic Design — DaVinci Resolve 20 New Features Guide — Resolve's current transcription and script-driven rough-cut capabilities.
• VEED — Edit by Script help — Current transcript deletion, restoration, filler-word and pause behavior, plus stated language and reordering limits.
• CapCut — Transcript Editing — CapCut's current transcript panel, filler-word detection, speech-gap cleanup, and timeline handoff.
• Carnegie Mellon — Simplifying Video Editing Using Metadata — The 2002 Silver paper describing synchronized storyboard, editable transcript, and timeline views.
• ACM UIST 2013 — Content-Based Tools for Editing Audio Stories — Transcript edits propagated to the corresponding speech track in a research production system.
• ACM UIST 2016 — QuickCut — Research on interactive transcript-driven editing for narrated video.
• OpenAI — Whisper paper — The speech-recognition architecture and time-aligned transcription tokens behind a common ASR family.
• Princeton Graphics — Text-based Editing of Talking-head Video — The 2019 generative research system that synthesized altered speech and facial motion from transcript edits.

Related Terms

Other entries in the Valmera video editing glossary that touch this one:

• Word-level timestamps — The unit the whole workflow is built on. No per-word timing, no text-based editing.
• Transcription and ASR — Where the text comes from, and the error rate you inherit with it.
• Edit decision list — What a transcript deletion actually writes: source ranges, not pixels.
• Silence detection — The other index. Words say what survives; silence says where the join can hide.
• Jump cut — What a clean transcript edit looks like on the picture side when nothing covers it.
• B-roll — The standard fix for the visual discontinuity a text edit creates.
• J-cut and L-cut — Sound and picture cut at different moments — a thing a single text caret cannot express.
• Burned-in captions vs subtitles — The same transcript, used for display instead of for cutting.

Frequently Asked Questions

Skip the Deleting

Valmera indexes your footage word by word, then edits it from a sentence you type. Account creation and uploads are free; a subscription is required to edit.