The first time a host sends us an interview recorded through an interpreter, there is usually a note attached that says something like "sorry, it is long," and it always is, because a forty five minute conversation with a guest who answers in another language can easily come back as a ninety minute raw file, and that is before anybody has cut a single cough.
My editors in Dubai are the people behind Pixel Samy Podcast, and every episode they cut, interpreted or not, goes from raw camera files and audio to a finished version for YouTube, Spotify and your podcast host with a person making every decision. We are an English language editing team, which matters a lot here, right, because an interpreted interview is really two recordings braided together, the guest's original words and the interpreter's English version, and the edit has to decide how much of each the audience hears. Interpreted episodes tend to land in our longer tiers, and on the Starter plan that means 199 dollars when the finished episode stays within an hour and 260 when it stretches toward an hour and a half.
Consecutive interpretation, the most common setup on podcasts, means the guest speaks a passage, pauses, and the interpreter then repeats it in English, so every answer is heard twice in a row. Simultaneous interpretation means the interpreter speaks over the guest in real time, usually on a separate audio channel.
Why does a podcast interview with an interpreter take so much longer?
A podcast interview with an interpreter takes longer because in consecutive interpretation every question and every answer is spoken twice, once in the original language and once in the interpreter's English, with short pauses for note taking in between, so the raw recording can run close to double the length of the actual conversation, and the edit has to deal with that doubled runtime directly.
That doubling is the whole problem in one number, right, and it hits two audiences differently. A viewer who does not speak the guest's language sits through an answer they cannot understand, then hears it again in English, and by the third question a lot of them have quietly left. A viewer who does speak both languages hears everything twice.
So the edit is not just tidying, right. It is deciding, answer by answer, what the audience needs to hear in the original, what they need to hear in English, and what can go. The pauses while the interpreter checks their notes, the moments where the guest waits politely, the "can you repeat the last part" exchanges, those come out first. Then the real choices start.
How much of the original language should stay in the episode?
The original language should stay in an interpreted episode wherever the guest's own voice carries something the translation cannot, emotion, humour, emphasis or a well known phrase, and in a short opening burst on most answers so the audience hears who is really speaking, while the rest of each answer is carried by the interpreter's English to keep the episode at a watchable length.
There are basically four ways to structure it, and I lay them out for every host before we cut:
- Keep both in full, which is the most faithful version and the longest.
- Keep the first few seconds of each original answer, then cut to the interpreter.
- Lay the interpreter's English over the guest's original audio at a lower level.
- Run English only, with a note at the start that the guest spoke through an interpreter.
The second option is where most shows end up, because the audience hears the guest's real voice and tone on every answer, which keeps the person at the centre, and the runtime drops close to the length of the original conversation. The third option feels smooth, like a documentary, but it has a catch, which is that consecutive interpretation was not timed to sit on top of the original, so the English and the guest's mouth movements will drift apart, and on camera that can look odd unless we cut to the host or a wide shot while the English plays.
The fourth option suits audio heavy shows but loses the guest's face while their own words are spoken. Whatever you choose, keep it consistent across the episode, because switching approaches mid interview confuses people more than any of the four does on its own.
One thing we will not do is decide on our own which original language moments matter. My editors do not speak every language our hosts interview in, so we rely on markers from you or the interpreter, a timestamp and a word like "keep, emotional" or "keep, joke lands here," and we build around them.
Who is responsible for the accuracy of the translation?
The host and the interpreter are responsible for the accuracy of the translation in an interpreted podcast interview, because an editing team cutting in English cannot verify what was said in the original language, so the editor's job is to preserve the interpreter's English exactly as recorded, never paraphrase it, and flag any spot where the recording suggests the interpretation was corrected or unclear.
I want to be plain about this, right, because it protects you as much as us. If the interpreter softened a strong statement, or a figure was misheard, that is not something an English language editor can catch by listening, and it would be wrong for us to imply otherwise. What we can do is make the review easy. We note every moment where the interpreter hesitated, restarted or said "sorry, I mean," and we send those timestamps with the first cut so the interpreter can check them.
If a passage needs fixing after recording, the cleanest route is for the interpreter to record a short corrected line on a decent microphone and upload it, and we drop it into the edit and match the sound as closely as we can. That beats leaving an error in.
I can make an interpreted interview feel like a real conversation, but only the interpreter can tell you whether the English says what the guest meant.
How should captions work on an interpreted podcast episode?
Captions on an interpreted podcast episode should follow the English the audience actually hears, so the interpreter's words are captioned as spoken, the original language segments are labelled with a short caption naming the language, and if you want the original language transcribed or a translation shown under the guest's own voice, that is raised on the call and scoped with you before we start.
Captions do more work on an interpreted show than on any other kind, right, because they let a viewer follow the guest's original segment while it plays. The usual approach is simple. While the guest speaks, a caption reads something like "speaking Spanish" or the language in question, then the English captions run under the interpreter. Burned in captions on vertical clips come with every clip, at 25 dollars each, and full caption files for the main episode are scoped when we talk.
The spelling of names, places and technical terms is the part that goes wrong most often, especially when the guest mentions people or organisations from their own country. Send us a short glossary before the edit and the captions will be right first time. The general thinking behind accurate captions sits in podcast captions and subtitles, while adding caption tracks on the platform itself is covered in YouTube's help article on subtitles and captions.
How do you keep the pacing natural when every answer is heard twice?
The pacing of an interpreted interview stays natural when the editor removes the waiting, the note taking pauses and the repeat requests, keeps the guest on screen while the interpreter speaks so the audience watches the person and not the translator, and trims the host's questions so the interpreted version of each question is heard once, cleanly, rather than the host's question and its interpretation both.
A multi-camera setup helps a lot here. If you have a camera on the guest, one on the host and one on the interpreter or a wide shot, the editor can show the guest reacting while the English plays, which is what the viewer actually wants to see, the face of the person whose story it is. With one camera on a remote call, we work with what is in the frame, and the cut leans more on keeping the guest's video up during the English.
For instance, when the host asks a question in English and the interpreter repeats it to the guest, the audience only needs the English, so the interpreter's version can shrink to a second or two before the guest begins, which across a long interview saves several minutes nobody misses.
Quick honest question for you here: when you watched your last interpreted interview back, did you catch yourself skipping ahead during the second half of each answer? If you did, your audience did too, and that is exactly the part the edit fixes. Cutting filler from a host or guest without making them sound robotic is a skill of its own, and the way we cut filler words applies to interpreters as well.
How should I record an interview with an interpreter so it edits well?
An interview with an interpreter edits well when the guest, the interpreter and the host are each recorded on their own microphone and their own audio track, the interpreter sits slightly off the main shot or on their own camera, and you note any moments you already know you want to keep in the original language while you are still in the room.
Separate tracks are the big one, right, and I would push for them on every interpreted recording. If the guest and the interpreter share a microphone, their voices overlap at the handoff and the editor cannot cleanly lower one under the other. On a remote call, a platform that records each participant separately, such as Riverside, gives the editor far more control, and the general advice for remote sessions is in remote recording that does not sound remote.
Then upload everything, camera files, separate audio, your glossary and your keep markers, into the shared folder. Interpreted episodes often run long, and for very long ones the delivery can take a day more than usual, which we tell you when you book. If your guests are on the other side of the world from you as well, how files and feedback move across time zones is explained in how remote podcast editing works.
How much does editing an interpreted podcast interview cost?
Pricing for an interpreted podcast interview works on length, the same as every episode we edit at Pixel Samy Podcast, so a single camera interview that finishes under 90 minutes is 260 dollars on Starter, multi-camera versions move to the Studio plan, and anything longer, or anything involving original language captions, gets scoped and quoted on a call before we begin.
When I quote an interpreted episode, I look at the raw file and your chosen structure, because keeping both languages in full makes a much longer finished episode. Full plan details are in Pixel Samy Podcast pricing.
When is an editing team the wrong choice for an interpreted show?
An editing team is the wrong choice for an interpreted show when the episode needs to be fully published in the guest's language, when the translation itself has to be produced or checked after recording, or when the show needs dubbing, because those are jobs for a translation or localisation specialist who speaks both languages, and an English language editor cannot do them honestly.
If you are building a show for two language audiences at once, a host who speaks both, or a bilingual producer, will make better decisions than any editor working from markers, and our work with language teachers and translators in Monterey shows how bilingual episodes are handled differently. Where my team fits is the host who records a great guest through a good interpreter, wants the audience to hear that guest's real voice, and needs the episode to be watchable from start to finish. The interpreter carries the meaning across, and the edit just makes sure people stay long enough to hear it.
So yeah. That's my way of saying it.