GLWS · Photos and media
Build a personal media library and stream it to supported clients.
Common uses of Jellyfin.
Direct playback and transcoding have different CPU demands. Check client codecs and hardware requirements; a VPS does not imply access to a GPU.
Planning examples, not official minimum requirements.
Photos and media
Check the current supported operating systems, deployment methods, dependencies and licence terms. What you need depends on your workload, not just the application's name.
Large datasets and busy workloads can need far more memory, storage or different hardware. Any external API or service subscriptions are separate.
Read the Jellyfin documentation ↗ (opens in a new tab)Advice specific to this application.
Check the video, audio and subtitle formats supported by your devices. Direct playback can avoid substantial conversion work, while simultaneous transcodes may consume far more CPU. Plan storage and network transfer around the size of the media library and viewing habits.
Decide which clients need access and whether a private connection or HTTPS endpoint fits the setup. Keep administrator access restricted and retain the configuration and library metadata outside the server. Use media you own or have permission to share with the intended viewers.
Linux guides that help with this setup.
Read the basic resource indicators on Ubuntu 24.04 LTS and AlmaLinux 9, then identify where to investigate a slowdown.
Read guide →Allow the SSH port you actually use before enabling UFW or firewalld, then test access from another terminal.
Read guide →Create a compressed archive of your own project, verify it, and extract a test copy without overwriting the original files.
Read guide →Four steps that make the environment easier to maintain.
Read the publisher's instructions and choose a supported installation method.
Protect the dashboard, credentials and network endpoints before you expose any service.
Work out where the application keeps its state and store it separately from replaceable runtime files.
Back up the data and configuration, then check that you can restore them.
Run through it before and after you install.
$ application-checklist --name jellyfin
[ ] Supported deployment method
[ ] Authentication and access restrictions
[ ] Independent data backup
[ ] Updates and restoration tested
root@glws:~#
Quick answers before you choose resources.
No. The configurator only saves your application preference. It does not connect to any infrastructure or run an installer.
Use the planning example as a starting point only. Check the publisher's requirements and measure the whole stack under a realistic workload.
You do. Self-hosted applications need updates, configuration and recovery planning from the operator. The publisher's documentation describes supported maintenance.
The knowledge base covers Linux access, packages, services, firewalls and backups.
Other tools you might run alongside or instead.
Organise and browse a personal photo library with mobile uploads and searchable albums.
Explore application →Website, email, DNS and database management in a hosting dashboard.
Explore application →A self-hosted assistant for connecting model-powered tasks with tools and messaging.
Explore application →An agent workspace for conversations, tools and automation on infrastructure you control.
Explore application →