How to speed up a zoom recording for rewatch
- Step 1Drop the meeting recording in — Accepts MP4, MOV, MKV, WebM, AVI, M4V, TS — covering Zoom MP4, Teams MP4, and Google Meet (Drive) exports. The file is read locally; nothing uploads. Speed change needs a Pro subscription (£7/month). The file card shows duration.
- Step 2Pick the speed for the meeting's pace —
1.5is the meeting sweet spot — fast but every speaker stays clear, and it's a single atempo pass. Use2for slow, monologue-heavy calls;1.25for a near-real-time archive copy. Type it in the Speed (× · 0.25 to 4) field. - Step 3Work out the new runtime — Output ≈ input ÷ speed. A 60:00 call is 40:00 at 1.5×, 30:00 at 2×, 48:00 at 1.25×. Choose the speed that gets the runtime to something a colleague will actually rewatch.
- Step 4Run the speed change — Click Run Speed. FFmpeg builds
[0:v]setpts=...[v];[0:a]atempo=...[a](a single atempo pass at 1.5× and 2×, cleanest for speech) and re-encodes to H.264 CRF 20 + AAC 192k. Progress shows in the dashboard. - Step 5Download and check overlapping speakers — Play a crosstalk section. At 2×, overlapping voices can blur; if so, re-run at 1.75× or 1.5×. The result is a normal MP4 download (no streaming-to-disk for this tool).
- Step 6Mute or trim sensitive bits first if needed — Speeding up doesn't redact anything. To remove a confidential segment before sharing the faster copy, mute that range with the audio mute region tool or cut it with the lossless trimmer, then apply speed.
Recommended meeting speed by call type
For multi-speaker comprehension, 1.5× is safest (single atempo pass). 2× suits slow, single-speaker calls. Output runtime shown for a 60-minute recording.
| Call type | Suggested speed | 60:00 becomes | Why |
|---|---|---|---|
| Fast crosstalk / brainstorm | 1.25×–1.5× | 48:00 – 40:00 | Overlapping speakers stay separable |
| Standard team meeting | 1.5× | 40:00 | Clear speech, meaningful time saved |
| Status update / report-out | 1.75× | ~34:00 | Mostly turn-taking, easy to follow |
| Lecture / single presenter | 2× | 30:00 | One voice, no crosstalk to blur |
| Archive copy (skim later) | 1.25× | 48:00 | Near-natural, slight time trim |
Speed value vs. filter chain (meeting range)
Filters built for common meeting speeds. Up to 2× is a single atempo pass — cleanest for speech intelligibility.
| Speed | setpts (video) | atempo (audio) | atempo passes |
|---|---|---|---|
1.25 | 0.8000*PTS | atempo=1.2500 | 1 (clean) |
1.5 | 0.6667*PTS | atempo=1.5000 | 1 (clean — meeting sweet spot) |
1.75 | 0.5714*PTS | atempo=1.7500 | 1 (clean) |
2 | 0.5000*PTS | atempo=2.0000 | 1 (clean, at the limit) |
Cookbook
Recipes for turning long Zoom, Teams, and Meet recordings into shorter, shareable rewatch files.
1-hour Zoom call to 40 minutes at 1.5×
The default move for meetings. 1.5× is a single clean atempo pass, so every speaker stays intelligible while you reclaim 20 minutes.
Speed field: 1.5 [0:v]setpts=0.6667*PTS[v];[0:a]atempo=1.5000[a] 60:00 input -> 40:00 output (H.264 MP4, AAC 192k) Voices clear and at original pitch
Single-presenter session at 2×
For a lecture or one-person report-out with no crosstalk, 2× is comfortable and halves the runtime.
Speed field: 2 [0:v]setpts=0.5000*PTS[v];[0:a]atempo=2.0000[a] 50:00 input -> 25:00 output Clean because there's a single voice to follow
Mute a confidential segment, then speed up
Speeding up doesn't redact. Mute the sensitive minutes first, then produce the faster shareable copy.
Step 1: audio-mute-region -> silence 12:00-14:30 (salary chat)
Step 2: speed-controller, Speed 1.5
58:00 -> ~38:40 shareable rewatch file
The muted range stays silent and is sped up like the rest.Drop overlapping crosstalk to 1.75×
When 2× makes a heated discussion blur, 1.75× keeps the back-and-forth followable while still saving time.
Speed field: 1.75 [0:v]setpts=0.5714*PTS[v];[0:a]atempo=1.7500[a] 45:00 input -> ~25:43 output, speakers stay separable
Trim the pre-roll, then speed the meeting
Meeting recordings often start with 'can everyone hear me?' Cut the waiting-room/setup minutes, then speed up.
Step 1: lossless-trimmer -> drop first 4 min of setup
64:00 -> 60:00
Step 2: speed-controller, Speed 1.5
60:00 -> 40:00Edge cases and what actually happens
2× blurs overlapping speakers on a busy call
Expected2× is clean for a single voice but crosstalk can run together. Drop to 1.75× or 1.5× — both single atempo passes — for clearer multi-speaker audio. There's no speaker-separation feature; choosing a gentler speed is the fix.
Screen-share-only recording with no audio
FailsA recording captured as screen-share with the mic off has no audio track. The filter graph always maps [0:a] through atempo, so a track-less file fails with a mapping error. Re-record with audio, or add a silent track first. Normal meeting recordings include audio and are unaffected.
Speeding up does not redact content
By designThe tool only changes pace — confidential discussion is still fully present, just faster. Before sharing a sped-up copy, mute sensitive ranges with audio mute region or cut them with the lossless trimmer. Speed is not a privacy operation.
Shared-screen text still readable after speed-up?
Preservedsetpts changes timing only, not resolution, so a shared slide deck or document in the recording stays as legible as the source. The CRF 20 re-encode is visually high quality; fine text in a 1080p meeting recording remains readable.
Variable-frame-rate meeting export
SupportedZoom/Teams/Meet recordings can be variable-frame-rate. setpts re-times by timestamp and the export is re-encoded H.264, so the faster file stays in audio/video sync. If a player previously drifted on the raw recording, the re-encode normalises it.
Output is MP4 even from a Teams/MKV recording
By designThe export is always H.264 MP4 + AAC, ideal for a wiki or knowledge base. If your archive specifically requires another container, run the MP4 through the transcoder.
Free tier — speed change gated
Pro requiredSpeeding up a recording requires Pro (£7/month); on free the run button is disabled with an upgrade prompt. File-size limits: Free 1 GB / 1 file, Pro 10 GB / 5 files, Pro + Media 100 GB / 50 files — no duration cap, so a long call is fine within the size limit.
Large file from sharing the recording link to Discord
Use the right toolSpeeding up shrinks runtime but not necessarily enough to hit a chat upload cap. To fit a recording under Discord's limit, use the Discord compressor, which size-targets the encode. Speed and size-targeting are different operations.
Batch of weekly recordings at one speed
Supported (batch)Drop several meeting files together to queue a batch (5 on Pro, 50 on Pro + Media). The same Speed applies to each — convenient for processing a backlog of weekly standups at a consistent 1.5×.
Long high-resolution recording is slow
May be slowAn hour of 1080p meeting re-encoded in the browser is CPU-heavy. It completes within your tier limit, but expect a wait. Trimming the dead pre-roll first speeds the job and the result.
Frequently asked questions
Will the speakers sound chipmunked at 1.5× or 2×?
No. The audio is time-stretched with atempo, which keeps the original pitch. A 1.5× or 2× meeting sounds like people talking briskly, not higher-pitched — which is exactly what you want when several voices need to stay intelligible.
What speed is best for a meeting recording?
1.5× is the sweet spot for multi-speaker calls — it's a single clean atempo pass and keeps everyone intelligible while saving a third of the runtime. Use 2× for single-presenter sessions with no crosstalk, or 1.25× for a near-real-time archive copy.
Does this give me a faster file or just faster playback?
A faster file. Unlike a player's speed slider, this re-encodes the recording at the new runtime, so you get an actual shorter MP4 to share with someone who missed the call, archive, or add to a knowledge base.
Is my meeting recording uploaded anywhere?
No. Everything runs in your browser via WebAssembly FFmpeg. Sensitive internal or client recordings are read locally and never sent to a server — only an anonymous 'file processed' counter is logged for dashboard stats. Good for confidentiality and compliance.
Can I redact a confidential part before sharing the faster copy?
Speeding up doesn't redact — the content is all there, just faster. Mute sensitive ranges with the audio mute region tool, or cut them with the lossless trimmer, and then apply speed to the cleaned recording.
Will shared slides or documents stay readable?
Yes. The speed filter changes only timing, not resolution, so a shared deck or document in the recording stays as legible as the original. The CRF 20 re-encode keeps fine text in a 1080p recording readable.
What format do I get back?
A standard H.264 MP4 (CRF 20, AAC 192 kbps) regardless of input — clean for a wiki, Drive, Notion, or knowledge base. If you need another container, run it through the transcoder.
My screen-share recording has no audio — why won't it process?
The filter graph always routes an audio stream through atempo. A screen-share captured with the mic off has no audio track, so the job fails. Re-record with audio, or add a silent track first. Recordings with participant audio process normally.
Can I process a backlog of weekly recordings at once?
Yes. Drop multiple files together to queue a batch — up to 5 on Pro or 50 on Pro + Media — and the same speed applies to each. That's ideal for taking a stack of weekly standups all to 1.5×.
How large a recording can I process?
Free allows up to 1 GB / one file, Pro up to 10 GB / five files, Pro + Media up to 100 GB / fifty files. There's no minutes cap — a long call is fine as long as it fits the file-size limit. Speed control requires the Pro tier (£7/month).
Speeding up didn't make my recording small enough to share — what now?
Speed changes runtime, not necessarily file size enough for a chat cap. To fit a platform limit like Discord's, use the Discord compressor, which targets a specific file size. You can speed up first, then compress the result.
Does setting speed to 1 do anything?
It re-encodes the recording to H.264/AAC MP4 without changing pace. If your goal is only to optimise a recording for streaming or shrink it, use the web optimizer or Discord compressor instead, which are built for that.
Privacy first
Every JAD Video tool runs entirely in your browser via WebCodecs and FFmpeg (WebAssembly). Your video files never leave your device — verified by zero outbound network requests during processing.