Convert PDF scripture to Logos and Olive Tree format

Extract verse-anchored text, build personal-book input, preserve footnotes and cross-references, validate verse counts before import.

How to convert PDF scripture to Logos and Olive Tree format

By ScoutMyTool Editorial Team · Last updated: 2026-05-28

Introduction

A pastor I work with had a study Bible as a PDF he wanted searchable inside Logos. Logos does not import PDF; it imports personal books with verse anchors. The bridge is a verse-tagger conversion that takes extracted PDF text, recognizes references like "1 Cor 13:1-13", wraps them with the milestone format Logos understands, and produces a DOCX the Personal Book Builder can consume. Same idea applies to Olive Tree, but with study-note formats. Here is the working pipeline for both, plus the verse-count validation step that catches conversion gaps before the personal book is built.

Vocabulary, quickly

TermMeaning
Personal bookLogos format for user-imported study content with verse anchors
Verse anchorTag like Gen 1:1 the app indexes for cross-reference
PBB / DOCX-LogosPersonal Book Builder formats Logos accepts
Olive Tree noteUser study-note format that can attach to a verse range
PericopeA defined passage of scripture treated as a unit
Cross-referenceLink from one verse to another verse or note
Study apparatusFootnotes, headings, and notes wrapped around the biblical text

Step by step

  1. Verify the translation\'s digital-use policy. Personal-use conversion is generally OK; redistribution is not. KJV/ASV are public domain.
  2. Extract text from the PDF. Use a text-extract that preserves reading order; OCR first if the PDF is scanned.
  3. Run a verse-tagger pass. Recognize references in multiple formats (Gen 1:1, Gen 1.1, Gn 1:1, 1 Cor 13:1-13) and wrap with milestones.
  4. Place footnotes adjacent to their verses. Extract footnote markers and bodies separately, relocate.
  5. Build the Logos DOCX or Olive Tree input. For Logos, use the Personal Book Builder style names (Heading 1 for book, Heading 2 for chapter, etc.). For Olive Tree, save as study notes with verse anchors.
  6. Validate verse counts. Compare source-PDF verse count to imported personal-book count. Gaps mean the verse-tagger missed a section.
  7. Compile and import. Personal Book Builder for Logos; Notes Import for Olive Tree. Spot-check three references after import.
  8. Add metadata. Title, author, source, edition date; the app uses these in the library view.

Personal-book QA checklist

  • Translation digital-use policy reviewed; conversion is personal-use only.
  • Verse counts match source PDF — gaps usually indicate a tagger miss.
  • Footnotes attached to the verse they explain, not floating at the end of chapters.
  • Cross-references resolve to the right verses in the personal book and to default scripture resources.
  • Library metadata (title, author, edition) set so the resource is searchable in the library view.
  • Parallel translations are imported as separate resources, not jumbled into one book.

Related reading and tools

FAQ

Why does Logos reject my PDF import?
Logos does not import PDF directly. It imports Personal Book Builder formats — DOCX with specific style names that map to chapters, sections, and verses, or RTF with verse milestones. A plain PDF has no semantics Logos can index. Convert the PDF to a verse-anchored DOCX first; then the Personal Book Builder produces a searchable personal book.
What is the simplest path from PDF to Olive Tree?
Extract text from the PDF, run a verse-tagger pass that wraps detected references with verse milestones, save as plain text or RTF, and import into Olive Tree as study notes attached to the relevant verse ranges. The verse tagger is the hard step — it needs to recognize "1 Cor 13:1-13", "Romans 8.28", and "Jn 3:16" as the same kind of reference.
How do I keep footnotes attached to the verses they explain?
During extraction, capture footnote markers in the body text and the footnote bodies separately; in the conversion, place footnote bodies adjacent to (or as Logos footnote elements on) the verse they reference. Most PDFs put footnotes at the bottom of the page; the conversion has to relocate them next to the verse marker.
My PDF has parallel translations side by side. Can Logos handle that?
Logos handles parallel translations as separate resources, not as a single combined personal book. Split the PDF columns into per-translation streams, convert each to its own personal book, and use Logos's parallel-resource layout to display them side by side. Trying to convert a parallel-column PDF as one personal book produces a jumbled output.
Are there copyright considerations?
Yes — modern translations (NIV, NLT, ESV, etc.) are under copyright and the publisher controls digital distribution. Personal-use conversion is generally permitted; redistribution of converted personal books is not. Public-domain translations (KJV, ASV) are unrestricted. Read the translation's digital-use policy before converting and never share the converted file beyond personal devices.
How do I verify the conversion preserved every verse?
Generate a verse-count report from the source PDF (count Gen 1:1, Gen 1:2, ... markers) and compare to the imported personal book. Missing verses are usually conversion-step artifacts — a chapter heading that confused the verse-tagger, a column break that swallowed a verse. Fix at the extractor settings; re-import.

Citations

  1. Wikipedia — “Logos Bible Software — personal book builder.” en.wikipedia.org/wiki/Logos_Bible_Software
  2. Wikipedia — “Olive Tree Bible Software — resource model.” en.wikipedia.org/wiki/Olive_Tree_Bible_Software
  3. Wikipedia — “Bible citation — reference formats.” en.wikipedia.org/wiki/Bible_citation

Convert scripture PDFs in your browser

Extract text, tag verses, place footnotes, validate counts — ScoutMyTool runs the whole pipeline locally so personal copies of copyrighted translations stay on your machine.

Open the PDF toolkit →