Audio and podcasting decision
AudioFetcher
A competent developer can reproduce the core converter and UI in about a week and run it cheaply; paid product extras (playlist UX, priority queues, billing) increase scope but are not technical moats.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Accept a YouTube URL, download the video, extract/encode MP3, store/serve the MP3 download, show conversion progress and results in a simple web UI
What it still won’t have
- Playlist import and selective playlist processing (Supporter feature)
- Priority processing / queued priority for paying users
- 320 kbps highest-quality MP3 for non-Pro users
- One-time Supporter Pass gating and built-in payments/billing UI
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 5 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal YouTube-to-MP3 web service using Node.js (Express), yt-dlp for downloads, FFmpeg for audio extraction, and S3-compatible object storage (or local disk). Scope: accept a YouTube URL (single video), download with yt-dlp, extract/encode MP3 at selectable bitrates (128/192/256), store the MP3 and return a download URL, provide a simple React or server-rendered form with progress polling and a conversions list. Out of scope: playlist import UI, paid billing system, priority queues, account management. Require: robust error handling for download/encode failures, input validation, timeouts, concurrency limits, and unit/integration tests for downloader, encoder, and storage operations.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score93
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official pricingAudioFetcher homepage
- official productAudioFetcher homepage features
- official productAudioFetcher Supporter details
- open sourceyt-dlp/yt-dlp
- open sourcealexta69/metube
Integrity checks
What held up, and what did not.
