How to Download Any Video in 10 Seconds Using the Terminal: A Practical Guide to `yoinks`

Say Goodbye to Ad-Filled Online Converters: Grab Any Video in 10 Seconds with yoinks

Over the years as a backend developer, I’ve frequently needed to save recordings from tech conferences, architecture breakdown tutorials, or live demo clips shared by peers on platforms like X/Twitter. My old workflow was painfully inefficient: I’d either open those sketchy "online video parser" websites, enduring endless pop-up ads, browser trackers, and artificial speed limits, or I’d waste hours configuring yt-dlp + ffmpeg locally. Even after setting it up, remembering long parameter chains was a chore, and one typo often resulted in out-of-sync audio/video or failed downloads. It was both time-consuming and frustrating.

Today, I want to show you how to completely ditch that hassle with a lightweight terminal tool called yoinks. The core logic is beautifully simple: copy the video link -> hit Enter in the terminal -> interactively pick your format -> auto-download to local storage. The whole process takes under 30 seconds. No ads, no hidden paywalls. By the end of this guide, you'll not only master the daily usage of this tool, but also understand how it automates underlying binaries, giving you a reliable "wrapper pattern" to improve CLI workflows for similar tasks.

Prerequisites

Before we begin, ensure your machine has Node.js 18+ installed. Why Node.js? Because yoinks is essentially a terminal UI app written in TypeScript, leveraging the Node ecosystem to automatically manage underlying binary dependencies. You don’t need Python pre-installed, nor do you have to manually download hundreds of megabytes of yt-dlp or ffmpeg—it handles all of that for you. If you use nvm or fnm, just switch to version 18 or higher. Open your terminal, and let's dive in.

Quick Start: Installation & Initialization

You have two installation options. If you want it available globally system-wide, run:

npm install -g yoinks
## Or run temporarily without installation
npx yoinks

On the first run, the terminal interface might pause for a few seconds. Don't panic—it's working silently in the background. It automatically fetches the latest standalone yt-dlp binary and saves it to ~/.yoinks/bin. This step completely frees you from Python environment dependencies. Simultaneously, it checks if ffmpeg is in your PATH (required for merging HD streams and mp3 encoding). If not found, it falls back to a built-in ffmpeg-static binary. This is why we call it "zero-config out-of-the-box"—it handles all the heavy lifting of environment setup.

In Action: Grabbing a Tech Video in 30 Seconds

Let's say you just watched a 40-minute YouTube talk on Kafka architecture optimization and want to save it offline for future reference. Run the command and paste the link:

yoinks https://www.youtube.com/watch?v=example123
## After running, use j/k or arrow keys to select resolution, then press Enter

After pasting and hitting Enter, the terminal takes over with a centered fullscreen UI, entering a format selector. Why use an interactive UI instead of raw CLI output? Because different platforms slice video streams differently. A single link might offer multiple streams: a 1080p video track, a separate audio track, and a pre-merged 720p stream. Manually crafting parameters often leads to downloading the wrong file or encountering sync issues. In the TUI, you can navigate using ↑/↓ or j/k keys. The bottom of the interface displays the estimated file size to help you manage disk space. Mouse support is also a neat bonus—just click to select.

Once you pick 1080p or Audio Only (mp3) and hit Enter, a full-screen progress bar appears. Upon completion, the file is automatically saved to ~/Downloads, and the terminal prints the full path. This default directory is a smart choice: it aligns with OS conventions, avoids permission errors, and lets you easily drag files into your IDE or note-taking app. The entire process runs purely in the terminal with zero web pop-ups, making it highly efficient.

Under the Hood & Troubleshooting Guide

1. Why no Python required? The author compiles yt-dlp into a standalone executable and invokes it via Node's child_process. This means developers get instant usability without dependency conflicts.
2. What if binary download fails on first run? This is usually a network environment issue. If your terminal routes through a proxy, ensure the underlying fetch request can bypass firewalls. Alternatively, you can manually place the yt-dlp binary into ~/.yoinks/bin beforehand.
3. Is the UI theme too harsh or hard to read? The default is auto mode, which adapts to your terminal background. If contrast is insufficient, run yoinks --theme light to force a light theme, or press ^T (Ctrl+T) during runtime to cycle through themes.
4. Can I script it for batch downloads? Currently, the project focuses on interactive TUI. The Roadmap hints at pure CLI flags like --best and --mp3 for non-interactive use. For now, if you need bulk archiving, stick to native yt-dlp. yoinks is optimized for quick, frictionless individual downloads.
5. Copyright Notice: The tool itself is a neutral technical implementation. Always respect platform Terms of Service and creator copyrights. Only download content for personal learning, technical review, or authorized archiving.

Summary & Next Steps

To recap, we've walked through the entire workflow: "Install -> Understand automatic dependency fetching -> Interactive format selection -> Local save". The brilliance of yoinks lies in not reinventing the wheel. Instead, it uses the excellent terminal UI framework Ink (React for Terminal) to wrap the powerful yt-dlp and ffmpeg into a "zero-config, mistake-proof" interactive experience. For developers who occasionally need to save videos or podcasts, it's more than sufficient.

Next steps: Add it to your .zshrc or .bashrc with an alias like alias yk='yoinks' for even faster access. If you plan to integrate downloading into CI/CD or automation pipelines, keep an eye out for the upcoming --best flag to script it directly in Shell. The true value of dev tools is "keeping the complexity under the hood and delivering simplicity to the user". Give it a try: copy your next link, and yoink it!