Repurpose a Podcast Episode into 10 Social Clips Automatically

The $500/Month Problem With Podcast Clipping Tools

You recorded a great podcast episode. Now you need 10 short clips for Instagram Reels, TikTok, YouTube Shorts, and LinkedIn. The obvious move is to sign up for Opus Clip or Riverside and let their AI pick the highlights.

That works until you're paying $39/month for limited clips, fighting an editor that won't let you customize output resolution, and waiting for a queue because everyone else on the platform had the same idea on Tuesday morning.

Podcast clipping SaaS tools like Opus Clip, Riverside, Podcastle, and Descript charge between $19 and $500 per month depending on volume. They control the output format, the encoding settings, and the workflow. If you're a solo creator on a budget, an agency processing dozens of episodes per week, or an automation builder wiring things into n8n or Make.com, that's a bad trade.

There's a simpler approach. FFmpeg can trim, resize, and overlay text on any video. FFmpeg Micro lets you run those same commands through an API without installing anything or managing a server.

TL;DR

This post walks through a 5-step pipeline to turn one podcast episode into 10 platform-ready social clips using FFmpeg commands, either locally or via the FFmpeg Micro API. Total cost with FFmpeg Micro: pennies per episode.

The Pipeline

The workflow has five parts. You start with one full-length podcast file and end with 10 clips, each sized and formatted for a specific platform.

Every step maps to a standard FFmpeg operation. That means you can run it on your laptop, on a server, or through FFmpeg Micro's API. Same commands either way.

Step-by-Step With Code

Trim a Clip

Say your best 45-second moment starts at 12 minutes and 30 seconds into the episode. With FFmpeg on the command line:

ffmpeg -i podcast.mp4 -ss 00:12:30 -t 00:00:45 -c copy clip1.mp4

The -ss flag sets the start time. -t sets the duration. -c copy skips re-encoding so it finishes in seconds.

The same trim through the FFmpeg Micro API:

{
  "inputs": [{"url": "https://storage.example.com/podcast-ep42.mp4"}],
  "outputFormat": "mp4",
  "options": [
    {"option": "-ss", "argument": "00:12:30"},
    {"option": "-t", "argument": "00:00:45"},
    {"option": "-c:v", "argument": "libx264"},
    {"option": "-crf", "argument": "23"}
  ]
}

Send that as a POST to https://api.ffmpeg-micro.com/v1/transcodes with your Bearer token. FFmpeg Micro handles the processing and returns the output file URL.

Resize for Vertical (9:16)

Instagram Reels, TikTok, and YouTube Shorts all want 1080x1920 vertical video. FFmpeg's scale and pad filters handle this cleanly:

ffmpeg -i clip1.mp4 -vf "scale=1080:1920:force_original_aspect_ratio=decrease,pad=1080:1920:(ow-iw)/2:(oh-ih)/2" vertical-clip1.mp4

This scales the video down to fit within 1080x1920, then pads the remaining space with black bars so nothing gets cropped. For a square LinkedIn or Twitter clip, swap the dimensions to 1080:1080.

Add a Text Overlay

You can burn a caption or episode title directly onto the clip using FFmpeg Micro's @text-overlay virtual option. This is useful for adding context when the clip plays on mute in someone's feed, which is most of the time.

For local FFmpeg, you'd use the drawtext filter. Through the API, the @text-overlay option simplifies it so you don't have to wrangle font paths and filter syntax in a JSON payload.

Batch All 10 Clips

You've got timestamps for 10 moments. Don't submit them one at a time. Script it.

#!/bin/bash
API_KEY="your-api-key"
SOURCE="https://storage.example.com/podcast-ep42.mp4"

declare -a STARTS=("00:02:15" "00:07:40" "00:12:30" "00:18:05" "00:23:50" "00:29:10" "00:34:22" "00:41:00" "00:47:15" "00:53:30")
declare -a DURATIONS=("00:00:40" "00:00:55" "00:00:45" "00:00:30" "00:01:00" "00:00:35" "00:00:50" "00:00:45" "00:00:40" "00:00:55")

for i in "${!STARTS[@]}"; do
  curl -X POST https://api.ffmpeg-micro.com/v1/transcodes \
    -H "Authorization: Bearer $API_KEY" \
    -H "Content-Type: application/json" \
    -d "{
      \"inputs\": [{\"url\": \"$SOURCE\"}],
      \"outputFormat\": \"mp4\",
      \"options\": [
        {\"option\": \"-ss\", \"argument\": \"${STARTS[$i]}\"},
        {\"option\": \"-t\", \"argument\": \"${DURATIONS[$i]}\"},
        {\"option\": \"-c:v\", \"argument\": \"libx264\"},
        {\"option\": \"-crf\", \"argument\": \"23\"}
      ]
    }"
  echo "Submitted clip $((i+1))"
done

That's 10 API calls. They process in parallel on FFmpeg Micro's infrastructure. If you're already using n8n or Make.com for your content workflow, you can wire this into an HTTP node instead of bash. Same payload, same endpoint.

What This Costs vs. Podcast Clipping SaaS

A 1-hour podcast split into 10 clips of 30-60 seconds each totals roughly 7 minutes of processing. With FFmpeg Micro's per-minute pricing, that costs pennies. Not $24. Not $39. Pennies.

The gap gets wider at scale. An agency processing 20 episodes per week would spend $100-$800/month on SaaS clipping tools. The same volume through FFmpeg Micro stays under a few dollars.

Common Pitfalls

Trimming on keyframes. Using -c copy (stream copy) is fast but only cuts on keyframes, which can mean your clip starts a second or two early. If precision matters, drop -c copy and let FFmpeg re-encode. Through the API, use -c:v libx264 instead.

Forgetting audio sync. When you re-encode video but copy the audio stream, you can get drift on longer clips. Use -c:a aac alongside your video codec to re-encode both.

Wrong pixel format for social platforms. Some social platforms reject videos with unusual pixel formats. Add -pix_fmt yuv420p to your options to stay compatible with every major platform.

Over-compressing for mobile. A CRF of 28+ looks fine on a desktop preview but falls apart on a phone screen at full brightness. Stick with CRF 23 or lower for social clips that people will watch on mobile.

FAQ

How do I automatically repurpose a podcast episode into social media clips?

Use FFmpeg to trim segments from the full episode with the -ss (start time) and -t (duration) flags, then resize each clip for the target platform. FFmpeg Micro's API lets you automate this without installing FFmpeg locally. Send one API call per clip with the timestamps and output settings.

Can I clip a podcast into vertical video for TikTok and Instagram Reels?

Yes. Use FFmpeg's scale and pad filters to resize any clip to 1080x1920 (9:16 aspect ratio). The command scale=1080:1920:force_original_aspect_ratio=decrease,pad=1080:1920:(ow-iw)/2:(oh-ih)/2 fits the video within the vertical frame and adds padding so nothing gets cut off.

How much does it cost to automate podcast clips compared to Opus Clip or Descript?

Opus Clip costs $19-$39/month, Descript costs $24-$33/month, and Riverside starts at $24/month. FFmpeg Micro charges per minute of processing with a free tier. Splitting a 1-hour podcast into 10 short clips costs pennies in API calls, making it significantly cheaper at any volume.

Can I add captions or text to podcast clips programmatically?

FFmpeg supports text overlays through the drawtext filter, and FFmpeg Micro provides a @text-overlay virtual option that simplifies the syntax for API use. You can burn episode titles, speaker names, or captions directly into each clip during processing.

What's the best way to batch-process multiple podcast clips at once?

Write a bash script or use an automation platform like n8n or Make.com to loop through your timestamps and send one FFmpeg Micro API call per clip. The clips process in parallel on the server side, so 10 clips don't take 10x longer than one.

FFmpeg Micro handles the video processing. You don't need to install FFmpeg, provision a server, or babysit encoding jobs. Get a free API key at ffmpeg-micro.com.

*Last verified: June 2026. API examples tested against FFmpeg Micro v1 endpoints.*