PDF to Podcast: How to Turn a PDF Into an AI Podcast

Why turn a PDF into a podcast?

Most PDFs get skimmed, saved for later, or never opened again. A report, a research paper or a long handout needs a desk and an hour of quiet. Few people have that hour.

As audio, the same document fits the commute, the walk or the gym. An AI podcast does not read the PDF aloud line by line. It explains it, in order, with transitions between the ideas, and adds the context a listener needs.

Which PDFs work best?

The importer reads the text layer of the PDF. If you can select and copy text in your PDF viewer, it will work. Good candidates:

• Reports and white papers. Annual reports, market reports and policy briefs. Dense text with a clear structure makes a strong episode.
• Research papers. One paper per episode. The script explains the question, the method and the findings in plain language.
• Handouts and course readers. Lecture handouts and compendia work well. For a full course, see the sibling guide on how to turn notes into a podcast.
• Ebooks and manuals you have the rights to. Product documentation, internal handbooks or a book you wrote yourself. One chapter at a time keeps the detail.
• Slides exported to PDF. The studio does not read slide files directly. Export the deck to PDF first. Decks with real sentences work; decks with three words per slide give the script little to go on.

Which PDFs do not work?

• Scanned PDFs. A scan is a picture of a page, with no text layer. The importer does not run text recognition (OCR) on images. If almost no text comes out, it stops and tells you the PDF has no text layer. Run the scan through an OCR tool first, or paste the text instead.
• Image-only pages. Pages that are only a photo, a chart or a diagram contribute no text. The rest of the document still imports, but the content of the images will not be in the episode. If a chart carries a key number, add it to the text by hand.
• Locked PDFs. Encrypted or password-protected files cannot be opened. Remove the protection (if you are allowed to) and import again.
• Very long files. A PDF can have at most 200 pages, and any upload can be at most 20 MB. Split a longer document into parts and make one episode per part.

What happens to a long PDF?

The studio works from up to 20,000 characters of material. A short PDF passes through as it is. A longer one is condensed into faithful working notes before it reaches you. The condensing step keeps the figures, dates, names, quotations and claims, and the document's own order and section headings. It drops boilerplate, legal notices and repetition. The text is rewritten into notes, not simply cut off at the limit.

The studio tells you how many words it found and whether the text was condensed. The extracted text lands in the material box, where you can read it, trim it or fix it before you generate. The file itself is never stored.

Condensing has a cost: a long report becomes notes, and notes lose detail. If one section matters most, make an episode from that section alone.

How to turn a PDF into a podcast in PodThis, step by step

This is the whole flow in the PodThis studio. You need a free account to import a file and generate an episode.

1. Open the File tab. The studio has four input tabs: Topic, Paste text, Link and File. Choose File.
2. Choose the PDF and confirm your rights. Pick the file and tick the box that says you have the right to use the document. Then click Import document.
3. Check the text. The extracted text appears in the material box. Skim it. Delete what you do not want in the episode, such as an appendix or a reference list.
4. Check the chapter plan. The AI reads the material and suggests chapters. You can edit chapter titles, remove chapters, or ask for different chapter ideas.
5. Pick a style. There are 12 styles. The next section shows which fit which kind of document.
6. Pick the language and visibility. The episode can be in any of 70 languages, so an English report can become an episode in another language. Visibility can be Public (listed in Discover), Unlisted (anyone with the link) or Private (only you). The default is Public.
7. Pick a length. Each length card shows its duration and credit cost.
8. Generate. It takes a few minutes, and you can follow the progress as it runs.

Which style fits which document?

• Documentary for reports, case studies and history. A narrator with expert voices carries the story, and the numbers land inside it.
• Educational for papers, handouts and manuals. A teacher and a learner work through the material step by step, and the learner asks the questions you would ask.
• Interview for Q&A material, policy documents and anything with a position to test. An interviewer presses an expert for real answers.

The other styles are built for stories, news briefings and entertainment. For a document, start with one of these three.

How long should the episode be?

Match the length to the document, not to your free time.

• Short (about 10 min, 1 credit): a brief, an article-length paper or one chapter.
• Standard (about 30 min, 3 credits): a full research paper or a mid-sized report.
• Deep Dive (about 60 min, 6 credits): a long report or a dense manual, where every section deserves time.

What you get

• A voiced episode with a full cast, built from your document and the context around it.
• Chapters that follow the structure of the document, so you can jump back to the section you need.
• A transcript you can read and search, and check against the PDF.
• Sources. The episode page lists the PDF first under "Sources & further reading", so listeners know what the episode was made from.
• Audio you can download and play anywhere, including offline.

Can you turn a PDF into a podcast for free?

Yes. A new account starts with 5 credits and gets 3 more every month. A Short episode costs 1 credit, so you can turn a few PDFs into podcasts each month without paying. Every style, length and language, and the File tab, is open on every plan; only the credits differ. See PodThis pricing and plans when you need more.

Tips for a better episode

• One document, one episode. Two unrelated PDFs in one episode give you a muddled episode.
• Trim before you generate. Cut the cover page, table of contents, references and appendices from the material box. The script spends its time on what is left.
• Rescue the charts. If a key finding lives only in a chart, type one sentence about it into the material box.
• Rename the chapters. Chapter titles that match the headings of the PDF make it easy to cross-check later.
• Read the transcript next to the PDF. It is the quickest way to catch a mistake before you share the episode.

Limits and honest caveats

• AI can make mistakes. The script can misread a table, round a number or state something more firmly than the document does. Check every figure you will repeat against the PDF. Our editorial policy explains what is and is not reviewed by a person.
• It researches around your document. The pipeline treats your PDF as the primary source and adds context from outside it. That helps understanding, but when the episode and the document disagree, the document wins.
• Respect copyright. Your own reports are yours. Papers, ebooks and manuals usually belong to their authors or publishers. Only upload what you have the right to use, and do not share episodes built from someone else’s work without permission.
• Keep confidential documents Private. For internal reports, contracts or anything under NDA, set visibility to Private before you generate. Check your organisation’s rules before you upload confidential material at all.
• Every episode says it is AI-generated. A short disclosure opens each episode, so nobody mistakes it for a recorded show.

Get started

Open the studio and turn your first PDF into a podcast. For what happens to an uploaded document and example episodes, see PDF to podcast: turning a document into an episode. For lecture notes and study material, read how to turn notes into a podcast.