Skip to main content

Contributing to Jellyfin

Thank you for your interest in contributing to the Jellyfin project! This page and its children describe the ways you can contribute, as well as some of our policies. This should help guide you through your first Issue or PR.

Even if you cannot contribute code, you can still help Jellyfin! The two main things you can help with are testing and creating issues. Contributing to code, documentation, translations, and other non-code components are all outlined in the sections below.

Reporting Issues

We use GitHub extensively to track open issues, new enhancements or features, and other aspects of development.

Please see the getting help page for help with troubleshooting and finding bugs, and the documentation on issues for more information on how to submit good issues.

Developing Code

The entire project consists of a C# core server, a JavaScript web client, and a number of other clients written in various languages and frameworks. If you have experience with these languages, we're always grateful for any contributions you might want to make!

For general guidelines on how the project works, including how to set up your development copy, make changes, and guidelines on Pull Requests (PRs), please see the documentation on contributing code. Jellyfin follows a "fork and PR" methodology; if you're not familiar with this, please see the relevant section.

Adding To Documentation

Documentation is incredibly helpful! All these docs are written using Docusaurus. You can find the raw markdown in the documentation repository. Pull requests are welcome!


If you're interested in helping to translate Jellyfin into your local language, we use Weblate running at to handle translations. These are collected in the translations branches of the various repositories and are merged into the master branches before each release.


Testing is the easiest way to contribute. Simply use Jellyfin, and if you run into problems, let us know. This is the most common way we uncover bugs, through a user doing something we hadn't thought about. If the issue does end up being related to the code, a bug issue can then be opened.