Convert Media URL to MP3 with FFmpeg in n8n Form Workflow
Convert Media URL to MP3 with FFmpeg in n8n Form Workflow
Regular price
£16.99
Regular price
£16.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
⚡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
Convert Media URL to MP3 with FFmpeg in n8n Form Workflow
Regular price
£16.99
Regular price
£16.99
Sale price
Unit price
/
per
Convert any direct media URL to an MP3 using FFmpeg—powered inside n8n
Send a media file URL into an n8n Form, let the workflow download the file, convert the audio to an MP3 with FFmpeg, and return the finished MP3 for download—all automatically.
What this workflow does
- Receives a direct media file URL submitted via an n8n Form trigger.
- Downloads the referenced audio/video file using an HTTP Request node and stores it as a binary file.
- Writes the downloaded binary to local disk so FFmpeg can process it (using the Read/Write File step).
- Runs FFmpeg locally (via an Execute Command node) to extract audio and convert it to MP3.
- Returns the converted MP3 by reading the MP3 from disk and using the form completion as a download response.
The conversion output is standardized to 44.1 kHz, 2-channel, 192 kbps MP3 as defined by the FFmpeg command in the workflow.
Use cases
- Media processing for SaaS operators: let users submit a direct file URL and instantly receive an MP3.
- Podcast/audio repurposing: convert audio from existing video/audio URLs into consistent MP3 files.
- Automation engineers: create a simple URL-to-MP3 endpoint inside n8n without building a custom service.
Technical details
- Nodes used: Form (trigger), Sticky Note (documentation), HTTP Request, Read/Write File, Execute Command.
- FFmpeg requirement: your n8n runtime must execute FFmpeg (FFmpeg installed and accessible on the PATH for the Execute Command step).
- Filesystem access: ensure the n8n instance can write to /home/node/.n8n-files/ (or update paths to a writable directory).
- Input requirement: use a direct media file URL (not a webpage/share link) so the HTTP download returns the actual media file.
