Start with the reading task
A folder of documents and a listening shelf have different needs even when they represent the same title. Decide whether the user needs text reading, audiobook playback or both. Jellyfin documents books and audiobook organisation, but its recognition of an item is only one part of the workflow. A particular reading or listening feature still depends on the client being used.
List a small sample of files you own or may distribute: one written book, one single-file audiobook and one audiobook split into parts. Record the title, author, format, number of parts, intended reader and desired progress behaviour. Keep text and audio versions identifiable instead of assuming that matching names create a synchronised read-along experience.
Give each title a clear boundary
Use a separate book-level directory so its content and supporting files have an obvious relationship. The official guide describes optional author grouping. It identifies embedded audio or EPUB metadata and book-level sidecars including content.opf, metadata.opf and ComicInfo.xml where applicable. Check the source relevant to the actual format rather than borrowing naming rules from a movie library.
Consider an original training handbook with a PDF and an audio edition. A useful inventory gives each edition a clear label and states whether they are independent items. If the audio is split into chapters, preserve the intended ordering and inspect the files' metadata before importing many titles. Do not rename chapter files solely to make a directory look tidy while ignoring the playback order the client exposes.
Separate metadata review from client review
Inspect the server result first: title identity, author, cover and the expected file or part count. If a wrong cover or author appears, compare the embedded and sidecar information with your inventory. Change one input at a time. Keep a copy of any hand-authored metadata so a later refresh does not leave you unable to explain the previous result.
Then use the intended client to check the actual task. For a written work, can the intended reader open the file and return to a useful position? For audio, can the listener select the right part and continue the next day? These are acceptance questions to carry out locally, not claims that every Jellyfin client implements the same reader or progress controls.
Preserve the distinction when expanding
After the sample, write a short collection policy covering title folders, edition labels, metadata ownership and the clients that were checked. Record limitations honestly. A readable PDF in one client does not establish compatibility for every book format, and a cover visible on the server does not demonstrate successful reading on a television.
Keep the original files and legal distribution terms with the collection. Library software neither supplies copyrighted books nor expands a licence to share them. Revisit the sample when changing the main client or server version. A small set of repeatable reading and listening checks is easier to maintain than a broad assertion that all books work.
Questions answered
Does Jellyfin provide synchronised text-and-audio reading?
The documented books guide does not establish a universal read-along workflow. Treat written and audio editions separately unless your actual client documents and demonstrates the required feature.
Can a book appear in the library yet fail in my reader?
Yes. Server recognition and client reading capabilities are separate checks; verify the specific format on the client you intend to use.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.