October 10, 2026 · 9 min read

Should a Podcast Editor Do a Free Test Edit? What I Tell Hosts Who Ask

Free or paid, what a fair podcast editor test edit looks like, what one segment can never prove about ten episodes, and the better way I suggest hosts judge an editor.

It is one of the most common questions I get on a first call, usually near the end, when the host has heard the process and the price and then asks, a little carefully, whether we would be willing to do a free test edit first, just a few minutes, just to see. And I understand exactly where that comes from, because hiring an editor is a leap of faith, you are handing over your voice, right, your guests and your reputation to someone you have known for fifteen minutes, so of course you want proof before you pay, and so the free test feels like the obvious, sensible, low-risk way to get it.

My honest view, after running a podcast editing team for a long time, is that the free test edit is a reasonable instinct that answers the wrong question. It tells you whether an editor can make three good minutes when they are trying very hard to impress you, and what you actually need to know is whether they will make your fortieth episode as carefully as your first, on time, without you chasing them. So let me go through what I tell hosts who ask, free versus paid, what a fair test actually looks like if you still want one, what no test can ever show you, and the way I think you should judge an editor instead.

Should a podcast editor do a free test edit at all?

Some will and some will not, and neither choice tells you much about quality on its own, so the better question is what kind of test would actually show you how they work.

There are good editors who happily do a short free sample because it wins them clients, and there are good editors who never do because they have been burned by people collecting free edits and disappearing, and the same is true of weak editors on both sides. So I would not treat a yes as a green light or a no as a red flag. What I would pay attention to is how they answer, right, whether they explain what they would need from you, what they would cut, how long it would take and what you would and would not be able to judge from it, because that conversation tells you more about the editor than the sample itself does.

The general framework for choosing someone lives on our how to choose a podcast editor page, and the test question is really just one small piece of that.

Why do some editors refuse free tests, and is that a bad sign?

Usually it is not a bad sign, because a free test costs a real editor real hours, and many have learned that a lot of free test requests never turn into paid work.

Think about what a proper test involves on the editor's side, right, because they have to download your files, sync the audio and the cameras, listen to the segment properly, make the cut decisions, colour it, mix it and export it, and if they are doing it honestly they are spending the same attention they would spend on paid work. For a solo freelancer that might be most of an evening, and if ten hosts a month ask for one, that is a lot of unpaid evenings. So when an editor says no, or says they will do it for a small fee, that is often just someone who values their time, and to be very honest I would rather hire that person than someone who will do unlimited free work for anybody who asks, because the second one is going to be stretched very thin by the time your show arrives.

The catch here is the opposite case. If an editor refuses a test and also refuses to show you real past work, refuses to explain their process and refuses to tell you what happens to your files, then the refusal is part of a pattern, and I wrote about that pattern on the post about podcast editor red flags.

What does a fair test edit actually look like?

A fair test is one real segment of your real footage, five to ten minutes, edited to the same standard as a full episode, with a short written note explaining the main decisions the editor made.

That is one, it has to be your footage, not a polished demo they already had lying around, because anyone can make their own best material look good, and what you want to see is what they do with your lighting, your guest's bad microphone and your habit of saying "you know" at the start of every answer. Secondly, it should be a hard segment, not the easy one, so pick the part with crosstalk, a guest who rambled, or a camera that drifted out of focus. And the third thing is the note, because a short explanation of why they cut what they cut shows you whether a human actually listened, right, or whether a tool just took out the gaps.

Give them the same brief you would give for a full episode, who the show is for, what your look is, a few past episodes to match, so the test is really a test and not a guessing game.

A fair podcast test edit in five stepsStep 1, Pick a hard segment: Five to ten minutes with crosstalk, rambling or a messy camera.. Step 2, Send the raw files: Original camera files and audio, not a compressed export.. Step 3, Give the real brief: Audience, look, and a few past episodes to match.. Step 4, Ask for a short note: Why they cut what they cut, in plain words.. Step 5, Judge it against your show: Listen on your phone, the way your audience does.A fair podcast test edit in five steps1Pick a hardsegmentFive to ten minutes withcrosstalk, rambling or amessy camera.2Send the raw filesOriginal camera files andaudio, not a compressedexport.3Give the realbriefAudience, look, and a fewpast episodes to match.4Ask for a shortnoteWhy they cut what they cut,in plain words.5Judge it againstyour showListen on your phone, theway your audience does.
A fair test uses your hardest real footage and the same brief a full episode would get.

What can a test edit never show you?

No test edit can show you consistency, meaning whether episode ten arrives on time and to the same standard as episode one, and consistency is most of what you are actually paying for.

This is the part I really really want hosts to hear. A test is a single performance under ideal conditions, right, the editor knows they are being judged, they have no other deadline on that file and they will spend whatever it takes, and so almost every test looks good. What it cannot tell you is what happens in week six when you upload late on a Friday, or in week nine when your guest's audio is a mess, or in week fourteen when the editor has picked up three new clients and your show is now the one they get to last. It cannot show you whether they reply when you message, whether revisions come back when promised, whether they keep your intro and lower thirds identical across months, or whether they hand over your project files if you leave.

A test edit shows you someone's best day, and a podcast lives or dies on their ordinary Tuesday.

You see the gap here, right, you are hiring for a long run of ordinary weeks, and a test only ever shows you one special week.

How do you judge a test edit once it comes back?

Listen to it the way your audience will, on your phone and at normal speed, and judge whether the conversation still sounds like a conversation, whether the audio is clean and level, and whether the look matches your show.

First, the cuts, do the answers still make sense, are thoughts left whole, does it feel natural or does it feel choppy, because choppiness is the classic sign of silence-detection auto cuts. Second, the audio, is it level between speakers, is the noise gone without making voices sound underwater, and does it sit around the loudness that platforms expect, which Apple describes on its audio requirements page as roughly -16 dB LKFS. Third, the look, does the colour match across cameras, do the lower thirds look like yours, and does the pacing feel like your previous episodes.

And then read the note. If it says something specific, like keeping a long pause because the guest was about to say something personal, that is a human who listened. If the note is vague or there is no note at all, that tells you something too.

Is a paid first episode a better test than a free sample?

For most hosts it is, because one full paid episode shows you the real process, the real turnaround and the real revision round, which a free sample of a few minutes never touches.

When you pay for a first episode you get the whole thing, the upload, the sync, the full cut, the colour, the mix, the graphics, the delivery time and the experience of sending notes and getting revisions back. That is the actual product, right, and if the editor works per episode with no lock-in, the risk is small, because you can simply stop after one if you are not happy. The page on the revision round that actually works covers what a good notes pass should feel like, and that is something you only find out by going through it once.

So my answer to most hosts, at the end of the day, is to treat the first paid episode as the test, judge it hard, and then decide.

What does a first episode cost with Pixel Samy Podcast?

Exactly what any later episode costs, so for a single camera show of up to an hour that is 199 dollars on our Starter plan, and nothing about it commits you to a second one.

If you film on several cameras the multi-cam plan applies instead, and every plan and length is on the pricing section, but the point I care about here is that there is no special trial version of the edit at Pixel Samy Podcast. The first episode goes through the same people and the same standard as the hundredth, which is the whole reason it works as a test, right, because you are looking at the product and not at a performance.

That one episode also shows you every stage you would live with afterwards, the upload, the two day wait for the first cut, your single round of notes and the corrected version arriving a working day later, and the sequence is written out on the how it works page, with the usual questions answered in the FAQ. Because each episode is paid for on its own, walking away after the first costs you that episode and nothing more, and the files from it are yours whatever you decide.

While you wait, keep a few simple notes, because this is the part of the test most hosts forget to run. Write down when you finished the upload and when the cut actually arrived, whether anyone asked you a sensible question about the show before starting, and how the reply felt when you sent your notes, quick and specific or slow and vague. None of that is visible in a three minute sample, and all of it is what your Tuesdays will feel like for the next year.

A better way to judge an editor across ten episodes

Judge them on a run, not a sample, so give the first three or four episodes a clear brief and then score each one on the same few things, cut quality, audio, look, timing and communication.

How much each method tells you about an editorA two by two map, horizontal axis from little effort for you to a lot of effort, vertical axis from tells you little to tells you a lot. Free three minute sample sits left and low; Portfolio of past episodes sits left and low; Fair test on a hard segment sits right and high; One paid full episode sits left and high; Four episode run, scored sits right and highHow much each method tells you about an editorlittle effort for youa lot of effort →↑ tells you a lottells you littleFree three minutesamplePortfolio of pastepisodesFair test on a hardsegmentOne paid full episodeFour episode run,scored
A judgment map, not data: the more of the real process you see, the more you learn.

Basically, a short run does what a test never can, it shows you whether the standard holds when the novelty wears off. If something slips, right, you will see it by episode three, and if nothing slips, you have your answer with far more confidence than any free sample could give. If you do decide to move on, the post on switching podcast editors without missing an episode shows how to do it cleanly, and the list of questions to ask a podcast editor helps you start the next conversation better. And if you would like me to look at your show, a short call of 15 minutes lets me see a recent episode and price it, or you can write to me at samy@pixelsamy.com, and either way I would much rather you judge us on a run of real episodes than on a few minutes we polished to impress you. So yeah. That's my way of saying it.

SamyFounder, Pixel Samy. I cut podcasts for a living and write down what works.

Ready to stop editing your own podcast?

Book 15 minutes. I will look at your last episode, tell you what I would change, and quote you on the call. No deck, no pitch.