Podcast and Spoken-Word Audio

How to export a podcast episode as a video for YouTube from REAPER

By StudioRescue Editorial

Published October 21, 2026

This is a delivery problem rather than an audio problem, and it catches people out because nothing about it is obvious from inside a DAW. You finish the episode, you go to upload it, and YouTube refuses the file. Google’s own help page is blunt about why: audio files like MP3, WAV or PCM “can’t be uploaded to create a YouTube video”, and it points you at editing software to convert them. A static picture with your audio under it counts as a video, and that is all you need to make.

REAPER can produce that file without any extra software, because it is a video-capable host and not only an audio one. The path is short once you know it. The part worth reading carefully is the render dialog, because what it offers you depends on your operating system and your build, and because the dialog changed earlier this year, so most tutorials and screenshots you will find no longer match what is in front of you.

First, decide whether you need to render anything

If you publish an audio-first show through an RSS feed, YouTube has a route that skips this job entirely. You connect the feed, and YouTube creates a static-image video from each episode using your show art and uploads it to your channel on your behalf. New episodes go up automatically as the feed updates.

It is genuinely less work, but it comes with conditions that are worth knowing before you commit to it:

• RSS ingestion is limited to select countries and regions.
• The content cannot contain advertisements. Sponsorships and branded content have to be disclosed.
• Episodes arrive private first, so you can wait for the back catalogue to finish uploading before making anything public.
• Audio cannot be updated once published. Fixing an episode means re-ingesting it, which creates a new video and makes the old one private.
• The result appears on YouTube and YouTube Music only, and every episode gets the same show art.

Render from REAPER instead when you want a different image per episode, when you want a title or any other graphic on screen, when the audio you are posting is not an RSS episode at all (a single, a demo reel, a voiceover sample), or when you want the file itself for somewhere other than YouTube.

Get the audio finished first

Nothing in the video step improves your sound, so treat the episode as finished before you start. If you are not sure the mix is ready to leave, the decisions are covered separately in podcast export settings in REAPER, and the loudness target in how to get your podcast to -16 LUFS in REAPER. Render the video from the same finished project, not from a re-imported MP3, so you are not stacking a second lossy encode on top of the first.

You also need a picture. Make it 1920 x 1080 so it matches what you are about to render. YouTube’s standard aspect ratio on a computer is 16:9, and the player adapts other shapes rather than rewarding them. A PNG or a JPG both work.

Put the picture in the project

1. Drag the image file into the project. REAPER imports still images as media items, so it lands on a track like any other item.
2. Drag the item’s right edge so it covers the whole episode from the first sample to the last. REAPER has a preference for the default length of an imported still image, so whatever length it arrives at is arbitrary rather than meaningful.
3. Open the video window with View › Video Window (Ctrl Shift V) and play a few seconds to confirm the picture is actually on screen.

Two things to watch here. If more than one track holds a video or image item, only the one on the higher track gets displayed, so keep the image on a single track and put it above the audio tracks if you want to avoid thinking about it. And if the picture does not fill the frame, the stock video processor includes a Resize track/item to project dimensions preset, which is the cleanest fix for an image whose proportions do not match the render size.

The render settings that match what YouTube asks for

Open File › Render. Most of this dialog is the same one you use for audio, and the general render settings behave exactly as they always do. The differences are all in the Output format section.

Set Output format to a video encoder. On macOS, REAPER encodes video out of the box through AVFoundation. On Windows it ships a limited build of FFmpeg, and there has also been a native Windows Media Foundation encoder for MPEG-4 since REAPER 6.57. Which of these your copy offers in that dropdown depends on your platform and build, so read what is actually there rather than hunting for a name from a tutorial.

Whichever encoder you land on, the target is the same:

Two naming notes that will save you some confusion. In REAPER 7.70 the format dropdown inside the video encoder settings was renamed file, so older guides point at a control that no longer has that label. And in 7.66 the FFmpeg encoder gained separate MOV and MP4 modes, which deprecated the old combined “QT/MOV/MP4” auto-select entry. If you are reading a tutorial that tells you to pick that combined option, it predates this change, and so does the wording in the current printed user guide.

One genuinely useful option is the pair of codec dropdowns: setting either one to None renders video-only or audio-only. That matters because it means the same dialog produces your audio deliverable and your video deliverable, and because MKV, which REAPER also offers as a container, is not on YouTube’s supported format list. Pick MP4 and ignore it.

If your build does not offer H.264 or AAC

This is the most common sticking point, and it is a build limitation rather than a mistake you made.

• On Windows, the bundled FFmpeg is deliberately limited. Cockos’ own instruction is to download the full FFmpeg libraries from ffmpeg.org and place the unzipped DLL files in REAPER’s UserPlugins folder, which you can find via Options › Show REAPER resource path in Explorer. Restart REAPER afterwards and the codec lists get longer.
• On macOS, the AVFoundation encoder writes .m4v and .mov only. That is not a dead end, because MOV is on YouTube’s supported list, so a MOV upload is fine. Install full FFmpeg if you specifically need an MP4.
• On either, WebM with VP8 video and Vorbis audio is a fallback that YouTube accepts, though it is not what Google recommends and there is no reason to prefer it.

Optional: something other than a flat image on screen

REAPER’s stock video processor ships presets that go a little further than a static picture, and they are free with the program. The ones relevant here are Image overlay and Text under Overlay, and, under Synthesis, Decorative Oscilloscope with Blitter and Decorative Spectrum Analyzer, which draw a moving waveform or spectrum from the audio.

Note the word Cockos chose: decorative. They are visuals, not meters, and nobody should read a level off them. They also turn a cheap encode into a real one, because every frame now has to be drawn rather than repeated, so expect a slower render and a bigger file. If you want a polished animated audiogram with captions, that is a video editing job and REAPER is the wrong tool for it.

What this will not do

• It will not improve the audio. The video wrapper is a container. Everything about how the episode sounds was decided before this step.
• It will not change how loud the episode plays back. Platforms adjust playback loudness on their own, which is a separate subject covered in why your vocal sounds thin and quiet after uploading.
• It will not give you chapters. Those are added on the YouTube side or in the feed, and the three different mechanisms are set out in how to add chapters to a podcast episode.
• It will not make YouTube treat the upload as a podcast. Appearing in YouTube’s podcast surfaces depends on how the show is set up on the platform, not on the file you hand it.
• It will not fix a picture that was never sharp. A 600 pixel cover scaled up to 1080p looks exactly as soft as it sounds.

Check these four things before you upload

1. Length. Play the very end of the rendered file. An image item that stopped short of the last word is the most common failure, and it is silent until you look for it.
2. Audio actually present. If a codec got left on None, you will have a perfectly valid video with no sound.
3. Dimensions. The file should report 1920 x 1080, not whatever your image happened to be.
4. Render bounds. As with any REAPER render, if the bounds were set to a time selection you will get that selection rather than the episode.