Okay, I have to admit something: I was editing in Descript like a total newbie for *months* before I finally sat down and learned the keyboard shortcuts. I was dragging clips, clicking endlessly... it was painful.
Once I committed the main ones to muscle memory, my editing speed probably tripled. It’s like switching from using a mouse for everything in Photoshop to actually using hotkeys. Game changer for cutting podcast interviews and cleaning up voiceovers.
Here’s my go-to cheat sheet—the ones I use constantly:
* **Spacebar** – Play/pause (this one’s obvious, but it’s the anchor)
* **I / O** – Set in and out points while playing. So much faster than dragging ends.
* **Cmd+K (Mac) / Ctrl+K (Win)** – Split clip at playhead. My most-used shortcut.
* **Shift+Cmd+K / Shift+Ctrl+K** – *Remove* the section between in and out points and close the gap. This is the magic "cut and ripple delete" combo.
* **` (Backtick)** – Toggle between the selected clip and the timeline. Saves so much scrolling.
* **Arrow Keys** – Left/Right moves playhead frame by frame. Up/Down jumps to next/previous clip boundary.
* **Shift+Delete** – Lift selection (removes it but leaves a gap).
For anyone doing A/B testing on their own video or audio content, faster editing means you can iterate on versions more quickly. I can now whip up two different intro variants for a landing page video in half the time.
What about you all? Any hidden shortcut gems I’m missing? I feel like I’ve only scratched the surface.
✌️
✌️
That muscle memory shift is real. I had the same experience years ago learning vim keybindings for coding - painful at first, then you can't work without them.
Your point about I/O keys being faster than dragging made me realize it's the same principle as defining job stages in a pipeline config versus clicking around in a UI. Reproducible, keyboard-driven workflows always win.
The backtick toggle is a smart feature. More tools should have that kind of context switching shortcut.
Build once, deploy everywhere
Exactly. The pipeline config analogy is spot on. Version-controlled config files are keyboard shortcuts for your CI/CD system. Can't reproduce a Jenkins job someone built by clicking through the UI six months ago.
Vim keybindings are the extreme case. Once you internalize them, any editor without modal editing feels broken. Same with automating deployment steps - once you script it, manual clicks feel like a waste of cycles.
YAML all the things.
You're singing my song with the Jenkins example. I can't count how many times I've inherited a "mystery box" pipeline built entirely through the web UI. Trying to reverse-engineer what someone clicked two years prior is a special kind of archaeology.
It's why my Ansible playbooks are my keyboard shortcuts for the entire homelab. Once you've felt the relief of `ansible-playbook restore-services.yml` at 2 AM instead of frantically clicking through five web consoles, there's no going back.
it worked on my machine