Free Podcast Tools for Recording, Editing & Publishing

Select an MP3, WAV or M4A and the browser reads the file locally to show its duration, format and file size. Two other modes handle the usual follow-up questions: add several clips together to see whether your segments fill a 30- or 45-minute slot, and estimate how large an episode will be at 64, 128 or 192 kbps before you export. Useful when a host caps upload size, or when a sponsor asks for exact runtime before the read is recorded. The page states local browser processing only — the file never leaves the tab.

Drag in an exported MP3 or WAV and read its integrated loudness next to the target that matters: −14 LUFS for Spotify and Amazon, −16 for Apple Podcasts, −19 for mono spoken word, −23 for EBU R128 broadcast. This is the number behind the most common podcast complaint — an episode that sounds quiet next to everything else in a listener’s queue even though the waveform looks full. If the check shows you are off target, the analyzer can produce a normalized MP3 to download. Processing happens in the browser; the page states no server upload.

Uses your microphone to measure the room before you record: a live meter plus a ten-second scan that reports the background level in dB. The reference bands are the useful part — below −60 dB is studio-quiet, around −50 dB is a normal room, −40 dB means a fan or air conditioner is audible, and above −30 dB the recording will need repair. Run it once with the room as you normally leave it, then again after you switch off the fridge or close the window. Microphone access only; nothing is recorded or stored.

Loads MP3, WAV or OGG clips into the tab, lets you drag them into order, and merges them into a single WAV you download — the files are processed locally, not uploaded. That covers the most common podcast assembly job: intro plus body plus outro, a sponsor slot inserted mid-episode, or several recorded segments joined after a break. Exporting WAV avoids the quality loss of re-encoding an already-compressed MP3. Long files need a short processing pause while the browser renders, so keep the tab open until the download starts.

A structured template builder rather than a chatbot. You fill in episode details, a one-line hook and your key topics or timestamps, and it assembles a formatted description you can paste into Spotify, Apple or your own site. The value is consistency: every episode ends up with the same sections, so listeners know where to look and show notes stop being an afterthought at one in the morning. Keep the hook to a single sentence and list six to ten timestamps; long lists read badly inside podcast apps.

Give it the show name, the audience and the episode topic, choose a tone — casual, professional, storytelling, energetic or interview — and it returns a skeleton intro: a hook, a one-sentence promise of what the episode covers, and a hand-off into the interview. Treat the result as a first draft and read it aloud once before recording; cut anything you would not actually say. Scripted intros work best at 20 to 30 seconds, ending with a reason to keep listening rather than a list of social handles.

Type a script and hear it read back using the voices already installed in your browser, with rate and pitch controls — no account, no credits, no audio sent anywhere. It is genuinely useful for checking rhythm: an ad read that looks fine on the page often turns out to be two sentences too long, or full of consonant clusters that trip a real voice. It also works as a scratch track when you are editing before recording narration. Voices differ by operating system, so the same text sounds different on Windows, macOS and Android.

Paste a transcript and get word count, character count, estimated speaking time at a normal podcast pace, and a frequency table of the words you actually repeat. Two practical uses: confirm an episode hits the length you promised, and catch verbal habits — “basically”, “you know”, a guest’s name used forty times — before publishing. Because it counts real text instead of guessing, it is also a quick way to compare a scripted segment against an improvised one. Text stays in the page and is not stored.

Builds a podcast RSS feed in the browser: show identity, Apple category, language and explicit flag, then one block per episode with title, description, audio URL and guid. The live XML pane updates as you type and shows whether the result is ready for Apple, and you can copy the XML or download rss.xml. What it does not do is host the file — you still need a stable URL for the XML and the audio, because directories poll that address. Treat the output as a starting point and validate it before submitting.

Paste your feed URL and it fetches the XML to check the fields Apple and Spotify actually require: channel title, link, description, artwork, language, and per-episode enclosure, guid and publication date. The report names what is missing or malformed instead of simply failing, which is the difference between “your feed is broken” and knowing which tag to change. Run it after every structural edit and again right before you submit to a directory. This is the one tool that needs a public URL — a feed sitting on your laptop cannot be checked.

Builds the metadata block for an episode file — title, artist, album, year, genre, comment and cover art — with a lock-screen preview so you can see what a listener will actually get. It outputs the exact ffmpeg command that applies those tags losslessly with -c copy, which is the step most GUI taggers hide. If you publish through a host, the host usually writes tags for you; this is for distributing files directly, archiving masters, or fixing an episode whose artwork never appeared in a player.

Upload artwork and see it inside Spotify’s player shape and Apple’s circular crop, with adjustable overlay opacity, so you can tell whether your logo or title survives the crop before you ship it. Podcast apps show the same square image at wildly different sizes; a design that looks balanced at 3000 pixels can lose its edges at thumbnail size. Apple asks for a square between 1400 and 3000 pixels, and text near the border is the usual casualty. The image is processed locally in the browser.

Enter the episode topic and choose a style — balanced, high-volume or niche — and it returns a hashtag set for Instagram, X or LinkedIn. Balanced mixes broad and specific tags and is usually the right default; high-volume tags bury small accounts; niche tags reach fewer people but convert better. Copy the set, then delete anything that does not describe the episode. Hashtags help an existing audience find a post; they do not create one, so treat them as distribution, not growth.