Why I built this

Book Search Party started as a fix for a boring problem

I kept bouncing between LibriVox, Gutenberg mirrors, random search results, and paid storefronts just to answer one simple question: where can I listen to this book right now? Book Search Party is my attempt to make that question much less annoying.

The short version

I wanted a cleaner way to discover audiobooks without pretending every listener is the same. Some days I want a free public-domain recording. Some days I want a polished professional narration and I am willing to pay for it. Most audiobook sites force you into one lane or the other, but real listening habits are messier than that.

So I built a search layer that lets me start with the book, then compare the listening options around it. If a title is free on LibriVox, great. If the same title also has a professional narration on Audiobooks.com or Audible, that matters too. The point is not to push one answer. The point is to make the choices legible.

What the site tries to do well

  • Surface audiobook pages from multiple sources in one searchable place.
  • Make free options easy to find without hiding the paid alternatives people compare them against.
  • Reduce dead ends by linking related books, genre pages, and listening guides.
  • Stay simple enough to run as a static site without heavy infrastructure.

Why the free sources matter

Book Search Party only makes sense because projects like LibriVox and Project Gutenberg have spent years building public resources that anyone can use. LibriVox volunteers record books that would otherwise sit quietly in the public domain. Project Gutenberg keeps the texts alive and searchable. Lit2Go has also done genuinely useful work for students, teachers, and listeners who want educational material without a paywall.

I do not want those sources buried under generic “content platform” language. They matter because they preserve access, they support readers with limited budgets, and they keep a huge amount of literature available outside closed subscription ecosystems.

Contact

If something is broken, misleading, or missing, email me at [email protected]. You can also leave product feedback on the public issue tracker.

I read both. Direct bug reports are especially useful when you can include the page URL that went wrong.