The library is new. The first books are still being produced, so the shelves may be empty or nearly empty when you visit. That is expected for now. This page describes how the library works, not what is on its shelves.

What it is

Firebrat Community is a small website with one job: help people find and share audiobooks that anyone may freely copy and listen to. It has three parts that fit together.

Because every book uses the standard package format, a book from the library opens in Firebrat exactly like one you converted yourself: sentence-by-sentence highlighting, tap-to-seek, and offline playback once downloaded. See DATA_SCHEMA.md for the format.

Listen and download

You can browse the library without an account. Signing in is needed to rate, comment, report, submit or save favourites.

On the web

On Android

Submit a book

You need a Firebrat account, a finished audiobook package, and the right to share it (see what counts as copyright-free). The Submit page is a four-step wizard: Source, Package check, Details and provenance, then Rights attestation and review.

The package

A zip (or an unzipped folder) containing manifest.json (schema version 1.0, book id, title, author, narrator voice, sections), sections/<id>/audio.m4a with its segments.json, and an assets/ folder. This is the same output the Firebrat converter makes, so any book you converted yourself already has the right shape. The wizard validates the manifest before you go on.

Two routes

Route A: I already have it on the Internet Archive

Paste the archive.org URL (a /details/ or /download/ link). The site checks live, through the Archive’s metadata API, that the item really contains your package.

Route B: upload it for me

The site uploads your zip to the Internet Archive from your browser, using your own Internet Archive S3 keys from archive.org/account/s3.php. The keys are kept in memory only: never stored, never logged, never sent to Firebrat’s database. If the upload fails, the page falls back to manual upload instructions and then to route A.

Why you choose your local file. archive.org downloads send no CORS headers, so a web page cannot read manifest.json from the Archive after the fact. Instead the wizard reads the manifest from your local copy of the zip or file, in your browser only, and stores the chapter list with the listing. Nothing from your machine is uploaded in route A. Audio then streams from the Archive with a plain audio element, which needs no CORS.

Status. Uploading from the browser (route B) has not yet been run against the live Internet Archive; only the preflight request was checked.

The “How this audio was made” section

Every submission must say how its audio was produced. It is shown to listeners on the book page, so nobody has to guess whether a voice is human or synthetic. You provide:

FieldWhat to enter
Generation methodFirebrat TTS, human-narrated, mixed, or other.
Narration engine and modelsWhich voice engine and which models (for example, the language model that cast the characters) were used.
Pipeline notesAnything a listener or reviewer should know about how the book was made.
Source textThe title and a link to the text the audio was made from.
LicencePublic domain, CC0, CC BY or CC BY-SA, with a link to the licence or the evidence for it.
AttestationA required tick box: you confirm you have the right to share the work under that licence.

Ratings, comments, reports and bugs

Copyright takedown notices

If you believe a book in the library infringes your copyright, you can send a notice. You do not need an account.

  1. Fill in the takedown form: the book, who you are, the work you own, the links you believe infringe, a good-faith statement, an accuracy statement and your signature.
  2. Admins review every notice. While it is open, an admin may disable the book by marking it disputed, so it stops being offered while the question is resolved.
  3. If the book’s submitter disagrees, a counter-notice can be sent through the GitHub issue link given on the legal page. No personal email address is published.

Please be accurate. A knowingly false claim can have legal consequences for the person who files it.

The copyright, terms and privacy pages in the library carry the full wording.

What is not finished. The database security rules for the library are written but have not yet been run in the Firestore emulator, and there is no rate limiting because the site has no server-side functions. Both are on the to-do list before the library is widely promoted.