forum.jellyfin.org

The Jellyfin Forum (forum.jellyfin.org) is organized into sections that separate official project news from community development work. If you want release news and blog posts, follow Project Announcements; if you want to track what contributors are building, follow the Development boards (Server, Web, Plugin, Packaging, and Client Development). Feature proposals live in Feature Requests, and forum policy changes appear in Forum Announcements. All of these sections are publicly readable; posting or replying requires an account, since the forum shows Login/Register prompts.

Official project news

Project Announcements

This is the board for announcements from the project about new releases, blog posts, and similar updates. It is the most direct place to learn that a new version or official post exists. The visible listing shows 71 threads and 1,837 posts, with a recent thread titled “Jellyfin for iOS 1.7.0” — an example of client release news appearing here.

Forum Announcements

This board covers the forum itself: policies, rules, and forum changes. The visible listing shows 4 threads and 6 posts, including an “Open call: MyBB Theme req...” thread. Check here when you want to know how the community is moderated or when the forum's own tooling changes.

Development discussions

The Development category is split by area of work, so you can follow only the part relevant to you:

These boards are for long-form discussion rather than quick questions. A thread like “[Release] JellyRoulette v...” in Plugin Development shows that plugin authors also post release notices there, so plugin users can watch that board for new plugin versions.

Feature Requests

Feature Requests is described as the place for long-form discussions about feature requests. With 398 threads and 1,192 posts, it is where proposals get debated rather than merely listed. If you want to know why a feature is or isn't being pursued, this is the board to read.

How to follow these sections in practice

1. Open forum.jellyfin.org and scan the board index. Announcements and Development appear as separate categories with thread and post counts, so you can judge activity before entering.
2. Enter the board that matches your interest — for example, Project Announcements for releases, or Server Development for server work.
3. Read the thread list. Thread titles and the “Last Post” column show what is newest; the index itself surfaces recent items such as the iOS release thread and a plugin release thread.
4. To reply, ask a follow-up, or start a thread, register or log in. The forum offers username/email and password login, plus login through a social network shown below the form.

A practical example: if you run Jellyfin in Docker and want to know about packaging changes, watch the Packaging board (11 threads, 30 posts) instead of General Questions. If you develop a client, Client Development and its platform sub-forums are the closer match.

What these boards are not for

General Questions (4,316 threads, 18,075 posts) and Troubleshooting (8,250 threads, 44,264 posts, with Networking & Access and Media Scanning & Identification sub-forums) handle usage help and problems. Project news and development talk belong in the Announcements and Development sections, which keeps release information and design discussion separate from support traffic.

The Jellyfin Forum at forum.jellyfin.org is the official community discussion site for the Jellyfin media server project. It is a MyBB-based bulletin board where you can read announcements, ask for help, follow development discussions, and share themes or guides. You can browse threads without an account; posting requires registering or logging in. The site also links out to the main Jellyfin website, GitHub, a status page, and the translation site, so it works as a hub rather than a standalone product page.

What you can find there

The forum is organized into three broad areas, each with a different purpose:

The thread and post counts visible on the index give a rough sense of where activity concentrates. Troubleshooting and General Questions carry the largest volumes, which fits a forum whose main job is helping people run their own server.

How to use it

1. Read first. Most common questions — installation, playback problems, plugin behavior — already have threads. Open the relevant section and scan titles before posting.
2. Pick the right section. A playback error belongs in Troubleshooting; a question about a Docker image belongs in Packaging; a request for a new feature belongs in Feature Requests.
3. Register to participate. The login and registration controls sit at the top of the page, and social-network login is offered as an alternative. An account is only needed when you want to post or reply.
4. Check the linked resources. For release notes and downloads, the main website and GitHub links in the header are the authoritative sources; the forum is where those changes get discussed.

What it is not

The forum is a discussion space, not a download portal or documentation site. It does not host the server software itself, and it is not a substitute for the project's official documentation. Treat answers from community members as peer advice: useful and often detailed, but not an official support contract. If you need to confirm a release date or a specific build, follow the Project Announcements section and the linked GitHub repository rather than relying on a single reply.

When it is worth visiting

• You hit an error during setup or playback and want to see whether others have solved it.
• You want to follow release announcements and project news in one place.
• You are developing a plugin, client, or theme and want feedback or to announce a release.
• You want to request a feature and see whether it has already been discussed.

If you only need to install Jellyfin or look up a configuration option, start with the main website and documentation; come to the forum when you need human answers, community examples, or a place to report a specific problem.

The Jellyfin Forum is a discussion site, not the project's main documentation hub. Its header and footer navigation include links out to the official Jellyfin website, GitHub, status page, translation site, and features/team pages, plus the forum's own Rules and Help pages. Use those links when you need project resources; use the forum itself when you need to ask or read a discussion.

The official links in the forum navigation

The forum's top and bottom navigation bars carry the same set of links. Based on the forum's navigation, they are:

The same block appears twice on the page — once at the top and once at the bottom — so you don't need to scroll back up to reach these links.

Where the forum fits in

The forum is organized for discussion, and the navigation reflects that. Below the header links, the index splits into three groups:

• Announcements — forum policies and rules, plus project announcements about new releases and blog posts.
• Support — Guides, Walkthroughs & Tutorials; Themes & Styles; General Questions; and Troubleshooting (with sub-forums for Networking & Access and Media Scanning & Identification).
• Development — Feature Requests, Server Development, Web Development, Plugin Development, Packaging, and Client Development (with sub-forums for Android, Android TV, Roku, and more).

There is also an Off Topic section for General Discussion. If your goal is to read release news, the Project Announcements section is the place; if you want to report or discuss a problem, Troubleshooting and its sub-forums are the relevant entry points.

A practical way to use these links

1. Start from the forum header or footer and open Website if you need general project information, or GitHub if you need code or issue tracking.
2. Check Status before assuming an outage is on your side, and Features before asking whether something is supported.
3. Read Rules before your first post, and use Help if the posting interface is unclear.
4. Return to the forum's Support sections to ask questions or search existing threads.

One caveat: the forum navigation tells you where these resources live, but it doesn't describe their contents. Treat the links as entry points and read the destination pages for specifics.

Post in Guides, Walkthroughs & Tutorials if you are sharing a how-to, in General Questions for broad questions about anything Jellyfin, in Troubleshooting (or its sub-forums Networking & Access and Media Scanning & Identification) for a broken setup, in Themes & Styles for customization, and in Feature Requests for long-form feature discussion. Reserve the Development sections for contributor work, not end-user support.

Quick section picker

How to choose between the close calls

General Questions vs. Troubleshooting

Use General Questions when you want an answer, an opinion, or a starting point — for example, "Where do I start?" style threads that already live in that section. Use Troubleshooting when something is actually failing and you need it fixed. The Troubleshooting section is by far the busiest support area, and it splits into two sub-forums:

• Networking & Access — remote access, ports, reverse proxies, connection and login problems.
• Media Scanning & Identification — libraries not populating, wrong metadata, mismatched titles.

If your problem clearly fits one of those two, post in the sub-forum rather than the parent; it puts your thread in front of the people watching that topic.

Themes & Styles vs. Feature Requests

Themes & Styles is for what you can change yourself today — themes, styling, and customization of your instance. Feature Requests is for long-form discussion about changing Jellyfin itself. If you want a built-in option rather than a workaround, that belongs in Feature Requests.

Support vs. Development

The Development sections — Server Development, Web Development, Plugin Development, Packaging, and Client Development — are for people working on the codebase, plugins, packaging (Docker, APT, and similar), and clients. Client Development has its own sub-forums, including Android Development, Android TV Development, and Roku Development. These are contributor discussions, not a faster route to end-user help; a "how do I fix my library" question posted there is likely to be moved or ignored.

Before you post

1. Search first. The support sections carry tens of thousands of posts, so your issue has likely been discussed. Check the relevant section and its sub-forums before starting a thread.
2. Pick the narrowest correct section. Troubleshooting sub-forums beat the parent; a specific Development area beats a general one.
3. Read the rules. Forum policies and rules are linked from the site's Help and Rules pages and announced in Forum Announcements, alongside project news in Project Announcements.
4. Expect to log in to post. The forum presents login and registration options, including social-network login, before you can participate.

Common mistakes

• Posting a setup failure in General Questions when it belongs in Troubleshooting — you lose the sub-forum audience that knows the answer.
• Filing a bug report as a Feature Request, or a feature idea as a support thread.
• Asking for help in a Development section because it looks more technical.
• Skipping the search and re-asking a question already answered in the same section.

If you are still unsure, General Questions is the safe default for anything that is not clearly a failure or a contribution.

Post your question in the most specific matching sub-forum, and include your Jellyfin server version, client and platform, the exact steps that trigger the problem, and the relevant log lines. Before posting, search the forum and read the rules linked from the index. The forum's own structure shows why this matters: Troubleshooting alone holds roughly 8,250 threads and 44,000 posts, so a vague question in a busy section is easy to lose.

Before You Post: Search and Read First

The Jellyfin Forum is a community support board, not a live chat. Its index lists these support areas:

Search Troubleshooting and General Questions first. With tens of thousands of existing posts, your error message or symptom has likely been discussed. Also check the Announcements sections and the Rules and Help links in the forum navigation, since policies and known issues are posted there.

Pick the Right Sub-Forum

Post where the people who know your problem actually read:

• Playback, connection, or access failures: Troubleshooting, and the Networking & Access sub-forum if remote access or reverse proxies are involved.
• Files not appearing, wrong metadata, or misidentified media: the Media Scanning & Identification sub-forum.
• Appearance and CSS changes: Themes & Styles.
• Plugin, server, web, or client code: the matching Development section (Plugin Development, Server Development, Web Development, Client Development, Packaging).
• Anything else: General Questions.

A thread in the right sub-forum reaches readers who have seen your failure mode before. The same question in General Questions competes with thousands of unrelated posts.

What to Include in Your Post

A useful help request answers these questions up front:

1. What you expected and what happened. One or two sentences, with the exact error text if there is one.
2. Steps to reproduce. "Open the Android TV app, select this movie, press play" is better than "playback is broken."
3. Server details. Jellyfin version (from the dashboard), operating system, install method (Docker, package, Windows installer), and whether hardware transcoding is enabled.
4. Client details. App name and version, device model, and network path (LAN, remote, VPN).
5. Logs. The relevant server log excerpt around the timestamp of the failure, plus client logs if the app offers them. Paste the lines in a code block rather than attaching a huge file.
6. What you already tried. Restarting, clearing the app cache, testing another client, and similar checks save responders a round of questions.

Example post skeleton

Title: Transcoding fails on Intel N100 after update to <version>

Server: Jellyfin <version>, Docker on Ubuntu 24.04, hardware acceleration = QSV
Client: Android TV app <version> on Chromecast with Google TV
Steps: Play 4K HEVC file from library -> spinner -> "Playback error"
Expected: Direct play or hardware transcode
Tried: Direct play works on web client; restarted container; same file fails on two TVs
Logs: [paste the ffmpeg and server log lines from the failed attempt]

Common Pitfalls

• Posting the same question in several sections. Pick one; duplicates split the answers.
• Omitting versions. Behavior changes between releases, and responders cannot guess your build.
• Pasting a whole log file. Trim to the failing request and the lines just before it.
• Asking for feature work in Troubleshooting. Feature Requests is the long-form discussion area for that.
• Ignoring forum rules. The Rules and Announcements links on the index describe posting expectations; read them before your first thread.

After You Post

Reply in the same thread with new findings rather than starting another. If a fix works, mark it clearly so the next person searching the same error finds the answer. That is how a forum with tens of thousands of troubleshooting posts stays useful.