Personal Books

Personal books (PBs) are user created resources with almost all the features of a Logos resource. They are built from Microsoft Word documents (.docx files) using the Personal Books tool and are fully incorporated into your Library.
With Logos 6 and higher, PBs may be synced across multiple desktop installations of Logos/Verbum, but currently Faithlife has no plans to support PBs on mobile apps.
Note: Personal books built in Libronix (Logos 3) are incompatible with this version of Logos.

Official Logos Videos include Personal Book Builder and PBB Harmonies and Lectionaries (v5.1+)
Official Logos Trainer, Morris Proctor, has excellent free Personal Book Videos.
Independent Trainer, John Fallahee, offers 2+ hours of Personal Book Builder.

Features that are tagged (v5.1+) cannot be compiled in Logos 4 but you can build the PB in Logos 5+ and scan it into v4.6c or higher.


To create PBs, you need to understand the types of tags that you can add to a document:

  • Milestones are not seen in the finished resource. They’re hidden markers that indicate the location in a resource. For example, in a Bible, a milestone is needed at every verse. In a Dictionary, a milestone is needed at the beginning of every article. In many resources, milestones are also added at the beginning of each page.
  • Datatype links are visible in the finished resource. As the name suggests, they add links to other resources or Bible passages. Datatype links don’t link to a specific resource, but to a datatype (such as Bible or Josephus). Logos will then open the link in the most highly prioritised resource that supports that datatype.
  • Resource links are also visible in the finished resource. As the name suggests, resource links link to specific resources, and optionally to a specific location in that resource.
  • Fields are also called Search Fields. A Bible resource can have fields like footnote, bible, heading, words-of-christ; where bible refers to the manuscript text and words-of-christ refers to the words (within bible) spoken by Jesus.



The syntax for milestones is [[@datatype:reference]]. For example:

  • [[@Headword:Rome]] It uses the language from the Word document, else specify @Headword+<language>
  • [[@Bible:jn 3:16]]
  • [[@GreekStrongs:G3056]]
  • [[@DayOfYear:January 17]] This would tend to be used in calendar devotionals that could be used in any year
  • [[@YearMonthDay:Jan 17, 2012]] This would tend to be used in lectionaries that would be used in a specific year
  • [[@Page:513]] or [[@VolumePage: 1,513]]

If you’re unsure how to find out the name of the datatype and reference, there are step-by-step instructions available.

The syntax for datatype links is very similar to milestones, but without the @ sign, and with an optional label [[label >> datatype:reference]]. For example:

  • [[Rome, City of >> Headword:Rome]] this will link to the current resource if the milestone is present
  • [[Bible:Jn 3:16]] most Bible links are created automatically, which means you don’t need to tag them – however, you may explicitly refer to a datatype with a certain verse-map, such as BibleLXX or BibleLUTBIB1984, see Bible Datatypes
  • [[GreekStrongs:G3056]]
  • [[DayOfYear:January 17]]
  • [[YearMonthDay:Jan 17, 2012]] the date may be given as mm/dd/yyyy, e.g. 01/17/2012 as well
  • [[Page:513]] Page numbers always link to the current resource

If you’re unsure how to find out the name of the datatype and reference, there are step-by-step instructions available. Note that Headwords in other resources have to be accessed as Resource links (below).

Open the resource to the desired place, select WIKI as the Copy Location method in the panel menu, then copy with Ctrl+Alt+C and paste the link with Ctrl+V. It uses the syntax [[label >> link]] so you can change the label as needed.


  • Copy Location now uses, which thankfully is a direct link when used in PB’s. Choose L4 for the logosres protocol and paste it into the link part of [[label >> link]].
  • Page offsets are not yet supported e.g. logosres:hlmnbblhbk;ref=Page.p_591;off=759 will go to the start of the page. It is possible to link directly to a heading, even if that heading is in the middle of the page, but doing so is rather fiddly.
  • To open a lectionary to today’s reading specify e.g. logosres:BCPDOLECT;

The Anatomy of a Link includes Bible and Headword examples (logosres only).


The syntax for Fields is {{field-on:<fieldname>}} ... {{field-off:<fieldname>}} OR use a Word style field:<fieldname>. For example:

  • {{field-on:Bible}}”For God so loved the world, {{field-off:Bible}}
  • {{bible-on}}”For God so loved the world, {{bible-off}}
  • If above text has a Style called field:RedLetter then it will be compiled as words-of-christ or WOC.

For a list of fieldnames see Search Fields List.

Text Input Box

The syntax for a text input box is {{input id=IDENTIFIER | type=text | lines=number | width=number | prompt=“text”}} where

  • ‘input id = IDENTIFIER’ is mandatory. The identifier value of the id attribute must be uppercase, start with a letter, and may consist of letters, numbers, underscores, hyphens, and periods. It must be unique within the resource e.g. QUESTION_1
  • ‘lines=number’ is optional. This controls the vertical size of the text box, in whole number line-heights. Default is 1.
  • ‘width=number’ is optional. This controls the horizontal size of the text box, in whole number character-widths.
    Note: you can only specify either lines or width. If both are given then the compiler will use lines and ignore width.
  • ‘prompt=“text”’ is optional. This may be used to specify text that will be displayed in the text box until the user inputs something.

For example {{input id=QUESTION_1 | type=text | width=35 | prompt=“Type”}}

Building Personal Books

Create the book

Your book is built from one or more Word .docx files. Add text or paste text from your original and add milestones, fields, links and other syntax elements as necessary. You can generate footnotes and use Word Heading styles for your articles/chapters as this will automatically generate a TOC. Text and syntax elements should use the Normal style and can be intermingled. Keep formatting consistent between the files of your book.

Note that milestones can be on the same line as the Heading because they are not visible in the resource, including TOC. Also remember that milestones are the only way to index the content of the article.

See Examples for other suggestions.

Build the book

  1. Go to Tools > Personal Books
  2. Click Add book
  3. Enter Title
  4. Enter Author (optional)
  5. Enter Copyright message and Description (optional)
  6. Choose the book Type (default: Monograph).
  7. Choose a Language (it is hoped that more will be added in the future)
  8. Click Add field for a menu of optional fields (Abbreviated Title is displayed)
  9. Optionally add a cover image: Click Change... under the blank book cover and choose an image file from your hard disk. You can find usable image files for most published books by searching for their title on Google Images
  10. Click Add file... and select the .docx file from your hard disk. You can add multiple .docx files to make up a book and use “drag&drop” to reorder them (right-click a file to remove it).
  11. Click Build book

After the book is built (aka “compiled”) it should automatically open in a tab and begin Indexing.

Rebuilding a Book

Make changes to your docx files, Add or remove any BODY FILES and then click Build book.
It will recompile, recreate the resource file and then Index it.

Problems you may encounter

  • If you get the message “Build Failed – Could not remove existing resource” it will advise you to close all open panels, but a restart works best.
  • You may still get some Warnings/Errors when the build succeeds, but they can be ignored if the document appears to be converted properly. View this PB errors page for more information and possible solutions.
  • Your milestones and links may appear to be correct but if they aren’t recognised by Logos you can often fix them in Microsoft Word by following these steps:
  1. Save your Word document as an RTF file and close it.
  2. Re-open the RTF file and Save as a Word .docx file.
  • Logos can crash without generating a log file. If this happens to you please send the document to so they can test the document.

If the document doesn’t get converted properly report the issue as a Bug on the appropriate Logos Forum.

Hints and Tips

First perform your search in the Search tool, then click on the Search menu and click on URL to copy the query to the clipboard. Then paste it into your document e.g. logos4:Search;kind=Basic;q=Word1_OR_Word2;match=stem

Consistent Formatting

Consistent formatting is essential to getting your links compiled correctly e.g. it is almost impossible to notice different styles having the same font+size. Here is the best way to achieve this in MS Word:-

  1. place your cursor somewhere in the document that has the desired formatting (style + font).
  2. press CTRL+SHIFT+C to copy the formatting
  3. select the text/link.
  4. right click> Styles> Clear formating (or select Clear All in the Styles box)
  5. press CTRL+SHIFT+V to paste the formatting.

Convert PDF to Word format

There are many free converters, mostly online. Afterward you may have to use your word processor to convert to docx.

A datatype reference, particularly bible ones, can display duplicated entries in a hover popup. The reference may look OK in the docx file and the resource but there is a hidden hyperlink. You can fix with Word’s Remove Hyperlink or select a number of references and use Ctrl+Shift+F9.

Ignore a reference

If you want a reference to be ignored by the compiler try the syntax {{~ reference }} (note the space before and after the reference).


Use the syntax [[label >> link]].


The ‘Lemma’ tab in the (right-click) context menu is not currently supported. But you can change the language setting in Word to Greek or Hebrew (after selecting the text) to get your prioritized lexicons in the lower portion of the context menu.

Pictures and Images

You can paste images from Logos or .bmp (bitmap) format directly into your document. Others must be inserted from the hard drive and with Text Wrapping (on right click menu) set to In Line.
Note: Neither method works with Word 2003, so you have to save to docx from Word 2007 or Skydrive.

Referencing milestones in your PB

A datatype link will not work as other resources will be prioritized for that datatype; Page being the only exception. A resource link can always be used but you can also use bookmarks & hyperlinks in your docx file e.g. a milestone for Mk 3:4 can be accessed by creating a bookmark at that place (Mk3_4) and then creating a hyperlink to that bookmark (you can even edit the Hyperlink style so that underscores do not appear). Power Tip: Using variables to Search and Replace in Word

Search Fields

Fields appear in the Search panel drop-down. Note that Red Letter text is “Words of Christ” and that you can only search for (tagged) Bible text in a Bible.

Search Results

Results appear in the Search panel under My Books but the section may need to be opened. Results from the Collections section of Passage Guide are also separated and PB’s will appear after any Logos books!

Searchable TOC Entries

If you want your TOC entries (Article heading, Chapters, Bible Book names, Pericope headings) to be searchable as a Heading field enclose them with {{field-on:Heading}} / {{field-off:Heading}} tags on separate lines.

Searching Bibles

You can use Bible Search for Bibles tagged with the bible search field, but Morph Search is not currently supported (see Lemmas).

Space is ignored (Workaround)

If space between words and codes (syntax) is ignored then expand the character spacing (Ctrl+D in Word 2007) by 1 or 2 pt.

Resource type requirements


  • create milestones for each verse
  • use the Bible field to separate bible text from verse numbers and headings, etc. Punctuation may safely be included, but use Text Compare to see what is showing up in your PB bible. For more see Bohuslav’s examples

Bible Apparatus

  • Has Bible milestones (like Bible Commentary); the primary content for each verse is critical apparatus notes.

Bible Commentary

  • Mark text which comments on a verse with a milestone like [[@Bible:jn 1:1]]
  • Commentaries usually comment on every verse

Bible Concordance

  • has headword milestones (like Dictionary below), but the primary content for each word is a list of verses in which that word appears. Use for backward compatibility with print books as the Search feature makes this type of book unnecessary in a digital library.

Bible Cross-Reference Index

  • Has Bible milestones (like Bible Commentary); the primary content for each verse is references to other verses.

Bible Harmony

Bible Notes

  • see Bible Commentary. However, Bible Notes may not comment on every verse and have concise comments or study notes.
  • if your comment covers different passages then put milestones on successive lines.

Calendar Devotional

  • requires tag in the format of [[@DayOfYear:MMMM d]] e.g. [[@DayOfYear:January 17]].


  • Llke Bible Commentary, but has non-Bible milestones (e.g., Apostolic Fathers, Josephus, Shakespeare).

Cross-Reference Index

  • like Bible Cross-Reference Index, but has non-Bible milestones.


  • requires tags in the format [[@Headword:Your_Item]] e.g. Sin [[@Headword:Sin]].
  • see Building a Dictionary


  • used for “bible dictionaries”
  • see Dictionary above


  • requires tag in the format of [[@YearMonthDay:MMMM d, yyyy]] e.g. [[@YearMonthDay:Jan 17, 2012]]
    or [[@YearMonthDay:mm/dd/yyyy]] e.g. [[@YearMonthDay:01/17/2012]] .
  • see Lectionary and Harmony Support


  • used for original language words
  • see Dictionary above


  • a generic type, so no special requirements

Sermons and Illustrations

Logos Bible Software Wiki

Welcome, Guest! (sign in)