Why Does OverDrive Reject Ebooks?

1. No direct author submission path

OverDrive does not accept submissions from individual authors. Library catalog listing requires either an OverDrive publisher account (available to publishers with an established backlist; not designed for single-title indie authors) or distribution through an aggregator that has an OverDrive supply relationship — Draft2Digital, Smashwords, IngramSpark, PublishDrive, or StreetLib. Authors who expect a direct upload portal similar to KDP or Apple Books Connect will find no submission path. The aggregator handles ONIX delivery, DRM application, and the library account relationship on the author's behalf.

2. ONIX 3.0 metadata required for library catalog ingest

OverDrive uses ONIX 3.0 records — not EPUB OPF metadata — to populate library catalog entries: the data that librarians review when acquiring titles and that patrons search when browsing Libby. When the ONIX record sent by your aggregator is incomplete — missing subject classifications, BISAC codes, audience codes, or territorial rights declarations — the title may be accepted by your aggregator but fail to ingest correctly into OverDrive's catalog, or appear only in limited library systems with reduced metadata. Fields that appear optional in your aggregator's metadata form are often required for full library catalog visibility.

3. Pre-applied DRM conflicts with OverDrive's Adobe ADE licensing system

OverDrive applies Adobe Digital Editions (ADE) DRM to every ebook it distributes to library systems. EPUBs that already have DRM applied — from a separate DRM provider, from a prior distribution arrangement, or from an author who applied their own file protection — cannot be processed by OverDrive's licensing pipeline, which expects a clean, DRM-free EPUB to wrap in ADE at ingest. Submit a DRM-free EPUB to your aggregator and let OverDrive apply its own DRM after ingest. This is not a content or quality rejection; it is a technical incompatibility between incoming DRM and OverDrive's own licensing system.

4. Library content standards block titles that passed retail channels

Public library systems serve patrons of all ages and operate under community standards that differ from retail platforms. OverDrive applies content filtering beyond what D2D or IngramSpark require for retail distribution — explicit sexual content, graphic violence, and some dark fiction sub-genres are excluded from library catalog distribution even when the same title is available at retail. A title in D2D's Premium Catalog and distributed to Kobo and Apple Books may be separately blocked from OverDrive and Libby without notification from your aggregator unless you check your library channel distribution status explicitly in the dashboard.

5. ISBN required — no alternative identifier accepted for library catalogs

Library catalog systems require an ISBN-13 for every listed title. Unlike KDP (which generates its own ASIN) or some retail platforms that accept a UUID-based identifier, OverDrive's catalog integration requires a valid ISBN in the ONIX record. Free ISBNs provided by aggregators (D2D, PublishDrive) are accepted, but the ISBN must be consistent across your ONIX record, your EPUB's OPF dc:identifier field, and your cover barcode. A mismatch between any of these causes catalog ingest failures that may not surface as an explicit error message in your aggregator dashboard.

How do library patrons find and borrow my book?

Patrons find your title in their public library's Libby app catalog. When a library system acquires your title through OverDrive, patrons place holds and borrow it for a fixed lending period, after which the digital copy expires automatically. You don't interact with patrons directly — the relationship is between the library and OverDrive, with your aggregator as the supply intermediary.

Do I get paid for library borrows?

Yes — OverDrive pays a royalty per lending transaction, passed through your aggregator. The specific model (pay-per-borrow or metered access) and rate depend on how your aggregator has structured the OverDrive arrangement. D2D, IngramSpark, and PublishDrive each publish their library channel royalty terms in their help documentation.

My book is on D2D and showing on retail channels — why isn't it appearing in library catalogs?

Three common reasons: (1) library distribution was not opted into during D2D title setup — it is a separate distribution selection from retail and is not enabled by default; (2) your title's content category is filtered by OverDrive's library standards even though it passed D2D's retail distribution check; (3) your ONIX metadata record has incomplete subject classifications that prevent correct catalog ingest at OverDrive. Check your D2D distribution settings and ONIX metadata completeness before assuming a technical EPUB issue.