Prepare Audiobooks for Library Digital Catalogs

Library listening is not a side channel anymore. In 2025, readers using OverDrive’s Libby and Sora apps borrowed 315.9 million audiobooks — up 13% year over year — inside a network that logged 820.5 million total digital checkouts across ebooks, audiobooks, magazines, and comics (OverDrive). OverDrive reports serving more than 87,000 libraries and schools in 115 countries with that catalog (OverDrive).

If your audio strategy stops at consumer stores, you are leaving institutional discovery on the table. This guide is about preparing library-ready packages: listen-checked masters plus acquisition-friendly metadata — not about promising a Libby borrow on production day.

Key Takeaways

• Library audiobook borrowing is large and still growing (OverDrive Libby/Sora 2025).
• Separate three clocks: files ready, catalog available to selectors, and patron-borrowable after a library licenses the title.
• Ship chapter-aware masters and complete contributor/subject metadata; incomplete records stall acquisitions even when audio is clean.
• Produce on pricing, automate kicks via docs, and treat store/library submission as a later track (distribution).

Who this is for

• Publisher and aggregator ops leads routing titles into public-library and school digital catalogs
• Rights and metadata managers who own ONIX (or aggregator forms) for audio editions
• Small presses and agencies preparing institutional packages without a dedicated library sales desk

If you are still closing midlist production gaps before any channel work, start with the midsize publisher backlist guide. This post assumes you can produce masters and need the library distribution path to stop being guesswork.

Before you begin

What you need:

• Frozen manuscript and listen-checked chapter masters
• Clear audio rights for library/school territories you care about
• A unique audiobook product identifier (ISBN) when your partners require it
• Narrator or digital-voice credit language ready for disclosure
• A named owner for metadata QC (not “whoever uploads next”)
• Time: production can be same-day once text is frozen; library selection and patron live dates are not
• Difficulty: Intermediate — audio is the easy part compared with metadata and partner routing

Step 1: Map the three library clocks

Do not put “live in Libby” on the same sticky note as “masters delivered.”

OverDrive’s own publisher path is explicit: distribution agreement → content onboarding → Marketplace discovery → purchase → patron access in Libby or Sora (OverDrive Publishers). Smaller lists often reach the same apps through aggregators. Either way, selection is a fourth human step after your upload succeeds.

Information gain: Teams that market “in libraries” the day production finishes train authors and imprints to blame audio QC for acquisitions lag.

Step 2: Freeze audio like a product, not a demo

Library buyers hear the same defects retail listeners hear — and they evaluate catalogs at scale.

1. Export from the same source of truth as your ebook corrections.
2. Keep chapter breaks aligned with the print/ebook structure whenever the text allows.
3. Attach a pronunciation sheet for series names, places, and specialist terms.
4. Archive WAV/MP3 (or partner-required) masters outside any single vendor UI.
5. Confirm AI-disclosure and narrator credit strings before anyone opens an aggregator form.

Book Industry Communication’s Digital Audiobook Best Practice (March 2025) treats AI narration as another form of audio originator in the supply chain — not a separate fantasy workflow — and stresses that standards-compliant files and metadata drive automation (BIC). Your job is to hand partners something they can ingest without a rescue project.

Step 3: Build acquisition-ready metadata before you submit

Selectors skip thin records. Treat metadata as part of production, not an afterthought on upload day.

If your aggregator only exposes a subset of these fields, fill every one it offers. Empty subject codes are a silent “no” in a busy Marketplace week.

Step 4: Choose the on-ramp that matches your list size

Optional wide distribution after masters exist is a separate step on Audioworm (distribution). Keep consumer retail and library packages on one asset archive, two calendar tracks.

For the consumer-side reminder that files ready ≠ store live, point stakeholders at the distribution timelines guide — the same separation applies to institutional apps.

Step 5: Produce and QC with selector ears in mind

Usage-priced AI production lets you forecast a library sprint without guessing per-finished-hour after the fact.

• Pull character counts from the frozen file and check pricing before you greenlight a batch.
• Gate voices with written sample approval — series listeners notice continuity in Libby too.
• Run a defect listen on opening chapters, dialogue, proper nouns, and endings.
• Prefer targeted re-renders over regenerating an entire title because one name slipped.
• Batch project creation through the MCP & API docs when multiple ISBNs share a season.

What this is not: a claim that library systems will purchase every title you onboard. Catalog quality improves your odds; it does not replace collection-development judgment.

A two-week library-package cadence

Compress for short nonfiction; expand metadata review when you sell into both public and K–12 channels.

Common failure modes

1. Calling a title “in libraries” at master delivery — patrons cannot borrow what no system has licensed.
2. Reusing a print ISBN on the audio product — breaks retail and library matching.
3. Skipping digital-voice disclosure — creates trust and ingestion problems.
4. Empty subject/audience codes — invisible to the buyers you care about.
5. Leaving masters only inside an aggregator portal — always keep a rights-holder archive.

What to do next

1. Score three titles for library fit (rights clear, text frozen, QC owner named).
2. Produce and listen-check masters on Audioworm; confirm pricing against character counts.
3. Build the metadata packet before anyone clicks submit.
4. Enable library channels with your partner, or start OverDrive publisher onboarding if your volume warrants it.
5. Keep institutional calendars on a separate track from production via distribution, and automate batch kicks from the docs.

Library demand is already showing up in nine-figure checkout numbers. Your advantage is not a louder launch tweet — it is a package selectors can trust.