#jellyfin

This is unofficial audio client for app. Currently it supports macOS, iOS and android via APK file. I’m also working on adding Linux(deb) support and windows. github.com/avdept/JellyBoxPlayersourceforge.net/projects/jellybox.mirror Resources: jellyfin.org

I recently found myself trying to solve a problem that probably affects a fairly small group of people: I wanted a convenient way to browse and download books from my Jellyfin library using the web browser built into an e-ink Kindle.

Jellyfin already handles my book collection through the Bookshelf plugin, but its normal web interface was never designed for the Kindle’s limited experimental browser. Modern web applications tend to depend heavily on JavaScript, dynamic interfaces, large images, and browser features that older or lower-powered devices either handle poorly or do not support at all.

That led me to create KindleShelf.

KindleShelf is a small, self-hosted web frontend for Jellyfin book libraries. It runs alongside Jellyfin and provides a deliberately simple interface for browsing, searching, inspecting, and downloading books from an e-ink Kindle.

The project is available on GitHub:

Built for a Limited Browser

The Kindle browser is not exactly known for being fast or standards-complete. Instead of fighting against those limitations, KindleShelf embraces them.

Pages are rendered as straightforward HTML on the server. Navigation, sorting, searching, and pagination all use ordinary links and forms. JavaScript is not required, and even images can be disabled without making the interface unusable.

Book covers are requested at a maximum width of 120 pixels, keeping pages lightweight and more appropriate for an e-ink display.

The result is intentionally plain, but that is the point. KindleShelf is designed to remain usable on hardware that struggles with the average modern website.

Jellyfin Remains the Source of Truth

KindleShelf does not maintain a separate book database or require another copy of the library.

It connects to an existing Jellyfin server and reads the Books library managed by the Jellyfin Bookshelf plugin. Metadata, authors, covers, available formats, and downloads all come from Jellyfin.

KindleShelf currently recognizes common book and archive formats including:

EPUB

AZW and AZW3

MOBI

PDF

CBZ and CBR

ZIP, RAR, and 7Z

Actual availability depends on what Jellyfin and the Bookshelf plugin report for each item.

Because KindleShelf is read-only, it stays focused on its primary job: making an existing library accessible from a Kindle.

Keeping the Jellyfin API Key Off the Kindle

One of my main design requirements was that the Kindle should never receive the Jellyfin API key.

The browser communicates only with KindleShelf. KindleShelf then makes the necessary requests to Jellyfin from the server side.

That keeps the API key out of page source, browser history, bookmarks, and download URLs. The application also validates Jellyfin item identifiers and confirms that requested books belong to the configured library rather than accepting arbitrary file paths or upstream URLs.

For a basic trusted home network, KindleShelf can operate without a login. It can also be protected with HTTP Basic Authentication.

For a better multi-user setup, it supports Jellyfin Quick Connect.

Signing In with Jellyfin Quick Connect

Typing a long username and password through a Kindle browser would be miserable, so Quick Connect is a much better fit.

When Quick Connect authentication is enabled, KindleShelf displays a short authorization code. The user enters that code from another browser or Jellyfin application where they are already signed in, then returns to the Kindle and checks the authorization.

KindleShelf never receives the user’s Jellyfin password.

The resulting Jellyfin token is stored in a bounded, server-side, in-memory session. The Kindle receives only a random HTTP-only session cookie. Browsing, covers, and downloads then use that user’s own Jellyfin permissions.

This also means different users can access the same KindleShelf installation without exposing the entire book library to everyone who can reach it.

Downloading Without Loading the Entire Book into Memory

Book downloads are streamed through KindleShelf rather than being completely buffered by the application.

KindleShelf can forward safe HTTP range requests and preserve Jellyfin’s partial-content and file-size headers. This matters for larger books and for devices or browsers that may resume or request only part of a file.

Format support still varies between Kindle models. EPUB and Amazon-compatible formats are generally the best options, but KindleShelf presents whatever compatible files Jellyfin reports.

Easy to Self-Host

KindleShelf is written in Python and can be run directly during development, but Docker Compose is the intended deployment method.

The basic setup consists of providing:

The Jellyfin server URL

A Jellyfin API key

The name of the Books library

Then the service can be built and started with Docker Compose.

No persistent application volume is required. KindleShelf uses a bounded in-memory cache for metadata and covers, while Jellyfin remains responsible for the actual library.

It can connect to Jellyfin over a shared Docker network, through the host machine, or elsewhere on the local network.

Designed for Home Servers

My own use case is a self-hosted media environment, so KindleShelf is designed with that kind of deployment in mind.

A simple trusted-LAN installation can be exposed over local HTTP, which may be necessary for older Kindles that cannot negotiate modern TLS configurations.

For access beyond the local network, KindleShelf should be placed behind a reverse proxy with HTTPS and authentication. A VPN or network allow-list is also a sensible option.

I would strongly advise against weakening the TLS configuration of an otherwise secure public server solely to support an old Kindle browser. A separate, carefully isolated compatibility endpoint is a much safer approach.

What KindleShelf Is Not

KindleShelf is not intended to replace Jellyfin, Calibre, or a full ebook management platform.

It does not currently edit metadata, upload books, track reading progress, or perform library management. Its interface is intentionally narrow and read-only.

That limited scope helps keep the project small, predictable, and usable on the devices it targets.

Future Send-to-Kindle Support

One obvious future feature is the ability to send a selected book through Amazon’s Send to Kindle service.

That functionality is not implemented yet, but the project already includes an extension point for a future delivery service. A complete implementation could eventually support:

SMTP delivery

Per-user Send to Kindle addresses

Approved-sender configuration

Format conversion through Calibre

Delivery history

Duplicate-send prevention

For now, books are downloaded through the browser, but the architecture leaves room for a more convenient delivery workflow later.

Why Build Something This Specific?

KindleShelf is admittedly a niche project.

It exists at the intersection of self-hosting, Jellyfin, ebooks, and aging e-ink hardware. That is also what made it interesting to build.

Modern software often abandons older or less capable devices long before the hardware stops being useful. A Kindle is still an excellent reading device, even when its browser can't cope with modern web applications.

Sometimes the right solution is not to replace the hardware. It is to build a smaller, simpler interface that respects its limitations.

- installed linux on my, my dad's and my sister's computers

- gotten a grapheneos phone i'm trying open source apps on

- started baby's first mini homelab 🤩 yes it's just a raspberry pi with pihole and jellyfin so far but yk it always starts small

How to Build Your Own Self Hosted Jellyfin Media Server

Why Choose Jellyfin for Media Streaming

Jellyfin is a powerful, open-source media system that puts you in total control of your personal digital collection. By self-hosting, you eliminate subscription fees and keep your data private while streaming your movies, music, and photos to any device.

Complete ownership of your entertainment library

No hidden costs or premium paywalls

Cross-platform support for seamless playback

Getting Started with Server Installation

Setting up your own server is straightforward regardless of your technical background. The process involves installing the server application on your preferred hardware to act as a centralized hub for your media files.

Choose compatible hardware like a PC, NAS, or Raspberry Pi

Download and install the Jellyfin server application

Point the server to your local media directories

Configuring Your Media Library

Once the software is installed, you need to organize your files so the interface can display metadata like cover art, ratings, and actor bios. Jellyfin automatically fetches this information, creating a Netflix-like experience for your personal files.

Structure your media folders clearly by category

Adjust transcode settings to match your device capabilities

make a folder in your files. this is where all the media you want on jellyfin will live from now on. make a bunch of subfolders in the main one (called the "root folder") for each type of media you want stored (e.g. music, movies, books, shows, whatever)

download tailscale to all the devices you want jellyfin on (do NOT skip this i promise you will need it later)

complete tailscale signup procedures

download jellyfin

complete the setup wizard on jellyfin (dont bother with adding folders unless you really want to, you can deal with it later)

give jellyfin permission to access your files

yayy youre done with setup on device A. now download jellyfin or an associated player (finamp, fintunes, symfonium, manet, etc. im using finamp so my music keeps playing even if my phone is off) on device B and add your server link

"elliott what even is my server link" "elliott its not working" shhhh. i know. it took me 3 days to figure this shit out, future Q. i am here to help you. go to tailscale and find the IP address of device A or whatever device you set jellyfin up on

take that IP address (it should only be FOUR BIG NUMBERS. FOUR. and it will look something like <123.45.678.90> or whatever combination device A decided its address is) (NOT THE 127 OR 10 NUMBERS. DO NOT USE THOSE.) and type it in using this format <http://> <ipaddress:8096>

"elliott what even is 8096" i dont know. i wish i did. im pretty sure it just tells device B that its allowed to join the server but that has a 99% chance of being wrong. its what makes jellyfin work on Not Device A so im choosing to leave it at that

good job, you are officially set up on device B. now you can go back to the folder stuff and do all that for the next one billion hours

add a media folder of your choosing. title it whatever your heart desires. copy the file address for the folder youre storing x media in so jellyfin knows exactly what youre trying to put on there.

repeat step 12 forever and congratulations! you now have a personal media server

other stuff

remember to scan your folders so it actually knows to read the files

i highly recommend getting a physical server (if you havent already) but im using my laptop rn and it seems ok so far. just remember to be mindful of how much storage youre using and you should be fine