Vibecode AudioFetcher
track this build5 steps, step by step0%KINDA · weekend project
The core loop is genuinely one-shottable: a small local UI, yt-dlp for the fetch, ffmpeg for the encode, files land in a folder. What is not a one sitting is everything that makes a public converter feel reliable week after week · YouTube bot checks, cookies/PO tokens, geo blocks, fair queues, abuse protection, and a hosted path so non-technical people never open a terminal. Build the personal script; do not expect one prompt to replace a maintained public service.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of AudioFetcher. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # AudioFetcher indie build ## Goal Build the smallest trustworthy replacement for the core AudioFetcher workflow for one developer or a tiny team. ## Scope Accept a YouTube URL or playlist, download audio with yt-dlp, encode MP3 with ffmpeg, and save the file locally. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - hosted UI for non-technical users - playlist preview with per-track checkboxes - priority queue and 320 kbps Pro path - someone else fighting YouTube bot checks, PO tokens, and geo blocks - email magic-link Pro auth and fair multi-user queueing If those capabilities are essential, use yt-dlp instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a personal YouTube-to-MP3 tool to replace AudioFetcher for one user on my laptop. Requirements: - Python 3.11 + a tiny localhost Flask or Starlette app; one page with a URL field, quality select (128 / 192 / 256 / 320 kbps), and a Convert button. - On submit, shell out to yt-dlp to pull best audio only, then ffmpeg to CBR MP3 at the chosen bitrate. Write files into ./downloads with a safe title filename. - Support a single video URL and a playlist URL. For playlists, show a checkbox list of titles first (yt-dlp --flat-playlist --print), then convert only checked items one by one with a simple progress log on the page (SSE or polling). - Put YT_COOKIES_FILE and optional HTTP_PROXY in .env; pass them to yt-dlp when set. If yt-dlp returns LOGIN_REQUIRED or bot-check text, show that error plainly and tell me to export cookies from a logged-in browser. - Cap each job at 3 hours of media; reject live streams. No accounts, no cloud, no queue service for other users · this is just me. - Out of scope: multi-tenant fair queues, Stripe/Pro billing, magic-link auth, public abuse protection, mobile apps. - README: install yt-dlp + ffmpeg, how to export Netscape cookies, and a blunt note that YouTube blocks many datacenter IPs so a home machine or cookies may be required. ## Required capabilities - Python or Node - yt-dlp - ffmpeg - optional cookies or residential proxy if YouTube blocks datacenter IPs ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of AudioFetcher. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # AudioFetcher indie build ## Goal Build the smallest trustworthy replacement for the core AudioFetcher workflow for one developer or a tiny team. ## Scope Accept a YouTube URL or playlist, download audio with yt-dlp, encode MP3 with ffmpeg, and save the file locally. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - hosted UI for non-technical users - playlist preview with per-track checkboxes - priority queue and 320 kbps Pro path - someone else fighting YouTube bot checks, PO tokens, and geo blocks - email magic-link Pro auth and fair multi-user queueing If those capabilities are essential, use yt-dlp instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a personal YouTube-to-MP3 tool to replace AudioFetcher for one user on my laptop. Requirements: - Python 3.11 + a tiny localhost Flask or Starlette app; one page with a URL field, quality select (128 / 192 / 256 / 320 kbps), and a Convert button. - On submit, shell out to yt-dlp to pull best audio only, then ffmpeg to CBR MP3 at the chosen bitrate. Write files into ./downloads with a safe title filename. - Support a single video URL and a playlist URL. For playlists, show a checkbox list of titles first (yt-dlp --flat-playlist --print), then convert only checked items one by one with a simple progress log on the page (SSE or polling). - Put YT_COOKIES_FILE and optional HTTP_PROXY in .env; pass them to yt-dlp when set. If yt-dlp returns LOGIN_REQUIRED or bot-check text, show that error plainly and tell me to export cookies from a logged-in browser. - Cap each job at 3 hours of media; reject live streams. No accounts, no cloud, no queue service for other users · this is just me. - Out of scope: multi-tenant fair queues, Stripe/Pro billing, magic-link auth, public abuse protection, mobile apps. - README: install yt-dlp + ffmpeg, how to export Netscape cookies, and a blunt note that YouTube blocks many datacenter IPs so a home machine or cookies may be required. ## Required capabilities - Python or Node - yt-dlp - ffmpeg - optional cookies or residential proxy if YouTube blocks datacenter IPs ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of AudioFetcher. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # AudioFetcher product brief ## Problem The core loop is genuinely one-shottable: a small local UI, yt-dlp for the fetch, ffmpeg for the encode, files land in a folder. What is not a one sitting is everything that makes a public converter feel reliable week after week · YouTube bot checks, cookies/PO tokens, geo blocks, fair queues, abuse protection, and a hosted path so non-technical people never open a terminal. Build the personal script; do not expect one prompt to replace a maintained public service. ## Product outcome Accept a YouTube URL or playlist, download audio with yt-dlp, encode MP3 with ffmpeg, and save the file locally. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Python or Node - yt-dlp - ffmpeg - optional cookies or residential proxy if YouTube blocks datacenter IPs ## Explicit non-goals for v1 - hosted UI for non-technical users - playlist preview with per-track checkboxes - priority queue and 320 kbps Pro path - someone else fighting YouTube bot checks, PO tokens, and geo blocks - email magic-link Pro auth and fair multi-user queueing ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build me a personal YouTube-to-MP3 tool to replace AudioFetcher for one user on my laptop. Requirements: - Python 3.11 + a tiny localhost Flask or Starlette app; one page with a URL field, quality select (128 / 192 / 256 / 320 kbps), and a Convert button. - On submit, shell out to yt-dlp to pull best audio only, then ffmpeg to CBR MP3 at the chosen bitrate. Write files into ./downloads with a safe title filename. - Support a single video URL and a playlist URL. For playlists, show a checkbox list of titles first (yt-dlp --flat-playlist --print), then convert only checked items one by one with a simple progress log on the page (SSE or polling). - Put YT_COOKIES_FILE and optional HTTP_PROXY in .env; pass them to yt-dlp when set. If yt-dlp returns LOGIN_REQUIRED or bot-check text, show that error plainly and tell me to export cookies from a logged-in browser. - Cap each job at 3 hours of media; reject live streams. No accounts, no cloud, no queue service for other users · this is just me. - Out of scope: multi-tenant fair queues, Stripe/Pro billing, magic-link auth, public abuse protection, mobile apps. - README: install yt-dlp + ffmpeg, how to export Netscape cookies, and a blunt note that YouTube blocks many datacenter IPs so a home machine or cookies may be required. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted AudioFetcher capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# AudioFetcher indie build ## Goal Build the smallest trustworthy replacement for the core AudioFetcher workflow for one developer or a tiny team. ## Scope Accept a YouTube URL or playlist, download audio with yt-dlp, encode MP3 with ffmpeg, and save the file locally. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - hosted UI for non-technical users - playlist preview with per-track checkboxes - priority queue and 320 kbps Pro path - someone else fighting YouTube bot checks, PO tokens, and geo blocks - email magic-link Pro auth and fair multi-user queueing If those capabilities are essential, use yt-dlp instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build me a personal YouTube-to-MP3 tool to replace AudioFetcher for one user on my laptop. Requirements: - Python 3.11 + a tiny localhost Flask or Starlette app; one page with a URL field, quality select (128 / 192 / 256 / 320 kbps), and a Convert button. - On submit, shell out to yt-dlp to pull best audio only, then ffmpeg to CBR MP3 at the chosen bitrate. Write files into ./downloads with a safe title filename. - Support a single video URL and a playlist URL. For playlists, show a checkbox list of titles first (yt-dlp --flat-playlist --print), then convert only checked items one by one with a simple progress log on the page (SSE or polling). - Put YT_COOKIES_FILE and optional HTTP_PROXY in .env; pass them to yt-dlp when set. If yt-dlp returns LOGIN_REQUIRED or bot-check text, show that error plainly and tell me to export cookies from a logged-in browser. - Cap each job at 3 hours of media; reject live streams. No accounts, no cloud, no queue service for other users · this is just me. - Out of scope: multi-tenant fair queues, Stripe/Pro billing, magic-link auth, public abuse protection, mobile apps. - README: install yt-dlp + ffmpeg, how to export Netscape cookies, and a blunt note that YouTube blocks many datacenter IPs so a home machine or cookies may be required. ## Required capabilities - Python or Node - yt-dlp - ffmpeg - optional cookies or residential proxy if YouTube blocks datacenter IPs ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# AudioFetcher product brief ## Problem The core loop is genuinely one-shottable: a small local UI, yt-dlp for the fetch, ffmpeg for the encode, files land in a folder. What is not a one sitting is everything that makes a public converter feel reliable week after week · YouTube bot checks, cookies/PO tokens, geo blocks, fair queues, abuse protection, and a hosted path so non-technical people never open a terminal. Build the personal script; do not expect one prompt to replace a maintained public service. ## Product outcome Accept a YouTube URL or playlist, download audio with yt-dlp, encode MP3 with ffmpeg, and save the file locally. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Python or Node - yt-dlp - ffmpeg - optional cookies or residential proxy if YouTube blocks datacenter IPs ## Explicit non-goals for v1 - hosted UI for non-technical users - playlist preview with per-track checkboxes - priority queue and 320 kbps Pro path - someone else fighting YouTube bot checks, PO tokens, and geo blocks - email magic-link Pro auth and fair multi-user queueing ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build me a personal YouTube-to-MP3 tool to replace AudioFetcher for one user on my laptop. Requirements: - Python 3.11 + a tiny localhost Flask or Starlette app; one page with a URL field, quality select (128 / 192 / 256 / 320 kbps), and a Convert button. - On submit, shell out to yt-dlp to pull best audio only, then ffmpeg to CBR MP3 at the chosen bitrate. Write files into ./downloads with a safe title filename. - Support a single video URL and a playlist URL. For playlists, show a checkbox list of titles first (yt-dlp --flat-playlist --print), then convert only checked items one by one with a simple progress log on the page (SSE or polling). - Put YT_COOKIES_FILE and optional HTTP_PROXY in .env; pass them to yt-dlp when set. If yt-dlp returns LOGIN_REQUIRED or bot-check text, show that error plainly and tell me to export cookies from a logged-in browser. - Cap each job at 3 hours of media; reject live streams. No accounts, no cloud, no queue service for other users · this is just me. - Out of scope: multi-tenant fair queues, Stripe/Pro billing, magic-link auth, public abuse protection, mobile apps. - README: install yt-dlp + ffmpeg, how to export Netscape cookies, and a blunt note that YouTube blocks many datacenter IPs so a home machine or cookies may be required. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted AudioFetcher capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent
Power users already run yt-dlp. Everyone else pays to paste a link in a browser and get an MP3 without installing tools or debugging LOGIN_REQUIRED. The money is convenience plus the permanent maintenance of staying ahead of YouTube client checks, not a novel audio algorithm.
xhosted UI for non-technical users
xplaylist preview with per-track checkboxes
xpriority queue and 320 kbps Pro path
xsomeone else fighting YouTube bot checks, PO tokens, and geo blocks
xemail magic-link Pro auth and fair multi-user queueing
share on X ↗"I just replaced AudioFetcher ($6/mo) with one prompt"
Don't feel like building it? These folks already made it free.
yt-dlpUgly, terminal-shaped, and still the downloader every prettier app quietly depends on.open source↗PParabolicA polite desktop face on yt-dlp; paste a playlist, pick MP3, go make tea.open source↗TTartubeA gloriously busy desktop queue for whole channels and playlists.open source↗all 3 free alternatives to AudioFetcher →· no votes, no pay-to-list · just what's real
AudioFetcher pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0/user | $0/user | 3 conversions/day; individual videos up to 20 minutes; up to 256 kbps; 0 playlist conversions; standard queue. |
| pro | $6/user | $4.92/user | Unlimited conversions; playlists; priority queue; 320 kbps output; videos up to 12 hours. |
| supporter pass | custom | — | 30 days of unlimited conversions; playlists; priority queue; 320 kbps; videos up to 12 hours. |
free tier3 conversions/day; individual videos up to 20 minutes; up to 256 kbps; 0 playlist conversions; standard queue.
billingPro is monthly + annual; Supporter Pass is a one-time $5 purchase for 30 days.
hidden costsThe service's official terms require users to convert only content they own or have permission to use.
verified 2026-08-12 · source ↗
Vibecode AudioFetcher
Kinda. The core of AudioFetcher is buildable in a weekend with the prompt on this page, but there are real gaps: hosted UI for non-technical users, playlist preview with per-track checkboxes. Read the honest list above before committing.
How much does AudioFetcher cost?
AudioFetcher costs about $6/month (Pro, checked 2026-07-30), which is $72 per year.
What do I lose by replacing AudioFetcher?
Honestly: hosted UI for non-technical users; playlist preview with per-track checkboxes; priority queue and 320 kbps Pro path; someone else fighting YouTube bot checks, PO tokens, and geo blocks; email magic-link Pro auth and fair multi-user queueing. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to AudioFetcher?
Yes: yt-dlp (Ugly, terminal-shaped, and still the downloader every prettier app quietly depends on.) Parabolic (A polite desktop face on yt-dlp; paste a playlist, pick MP3, go make tea.) Tartube (A gloriously busy desktop queue for whole channels and playlists.) All 3 curated free alternatives are at vibecodeit.com/audiofetcher/alternatives. The prompt is for when you want it exactly your way.