How to Use Owncast: The Beginner's Guide (First Install, the Stream-Key Lesson, OBS + RTMP, and the Federation Question)

CodexFuse Team · 2026-11-01T15:50:00.000Z · 15 min read min read

How to use Owncast: a complete beginner's guide to the single-user self-hosted live streaming server — install, admin, the stream-key lesson, OBS over RTMP, going live, chat, federation, and backups.

Learning how to use Owncast is how you run your own Twitch without Twitch in the middle — the practical self hosted twitch alternative for streamers who want to own their channel. Owncast is a free, open-source, single-user live video streaming and chat server that you self-host: you push it one live feed from OBS over RTMP, and it serves a polished watch page with built-in chat to your viewers, at your own domain, with no platform rules and no revenue cut. This owncast tutorial runs the complete beginner arc in one place: the mental model, what hardware you actually need, the three ways to install it, the admin panel, the stream-key lesson, connecting OBS, going live, the latency-versus-buffer tradeoff, chat and moderation, making it look like yours, the federation question, HTTPS behind a reverse proxy, and backups. If you have never touched Docker, start with our Docker beginner guide — the easiest install below assumes you can run one docker command.

What Is Owncast?

Owncast is an open source, self-hosted, decentralized, single-user live video streaming and chat server — that is the project's own description. Say the important part once: it is single-user by design, meaning one broadcaster and one channel, not a multi-channel platform. You send it one live video feed (typically from OBS over the RTMP protocol), and Owncast handles everything after: it transcodes your feed into multiple quality variants, serves them to viewers through a built-in web player, and gives those viewers a real-time chat room next to the video. There is no discovery algorithm, no partner program, no company between you and your audience, and no per-viewer hosting bill from a streaming platform. The current release is v0.3.0, released September 3, 2026, and every version number, port, and command in this guide was verified against the official Owncast documentation on November 1, 2026.

How Do You Use Owncast? The 9-Step Short Version

If you want the whole arc before the detail, this is how to use Owncast from zero to your first live stream:

1. Pick where it runs: a VPS with at least 2 CPU cores, 1–2 GB of RAM, and 5+ Mbps of upload for a smooth 720p stream.
2. Install it with the quick installer, a prebuilt binary, or one Docker command.
3. Open the admin at http://yourserver:8080/admin and change the defaults immediately — the admin login and the stream key both ship as guessable values.
4. Rotate the stream key and treat it like a password, because that is exactly what it is.
5. Connect OBS: Service set to Custom, Server rtmp://yourserver/live, stream key in the key field.
6. Go live, and set your expectation about latency: a few seconds of delay is normal and healthy.
7. Set up chat: appoint moderators and learn where the moderation tools live.
8. Make it yours: channel name, logo, description, favicon, and custom CSS.
9. Decide the federation question (it is opt-in, not automatic) and put HTTPS in front of the server.

What Hardware Does Owncast Need?

Transcoding is the expensive part, and it scales with the number of output quality variants you configure — more variants means more CPU. The requirements are modest by server standards, which is why Owncast runs happily on a cheap VPS.

Two refinements worth knowing for any self hosted streaming setup. First, hardware-accelerated encoding is supported (VA-API, NVENC, and OpenMAX on Raspberry Pi), which shifts the transcoding load off the CPU if your hardware has it. Second, upload bandwidth is the hard ceiling: your viewers pull the stream from your server, so a home connection with fast download but slow upload will cap your quality before your CPU does. If your audience is private — a team, a class, a community — our Tailscale beginner guide covers serving the stream over a private mesh instead of the public internet.

How Do You Install Owncast?

There are three real paths, plus a fourth for people who hate terminals. The official quick installer downloads the latest Owncast for your platform, and if ffmpeg is not installed it now fetches an Owncast-built ffmpeg binary for you — but the docs advise against running it as root and suggest reading the script before piping it to bash.

curl -s https://owncast.online/install.sh | bash

Pick the zip matching your machine's architecture (uname -m on Linux will tell you) if you go the binary route. The owncast docker path is the one this guide assumes for the rest of the walkthrough because it is the easiest to reason about: one container, one data directory, and a single volume to back up.

Where Is the Admin Panel, and What Must You Change First?

The owncast admin panel lives at http://yourserver:8080/admin, and the very first thing you do there is change the defaults. Out of the box the admin username is admin, the admin password is abc123, and the stream key is abc123 — the official docs say it is highly recommended that you change these values immediately after your first login, and they mean it. A server on the open internet with a guessable admin password and stream key is a server you will lose within the day. Change the admin credentials and the stream key in the admin dashboard before you touch anything else, and do it before you open port 8080 to the world if you can.

Why Is the Stream Key the Password?

The stream key is not a label or a setting you can share around — it is the credential that authorizes publishing to your channel, which makes it functionally a password. Anyone holding your key can push video to your channel, so rotate it to something long and random and never paste it in a public chat, a screenshot, or a forum post. One subtlety the docs are explicit about: the admin password and the stream key default to the same value (abc123), but they are separate settings — changing one does not change the other. Change both, and change the key again any time you suspect it leaked. Your owncast stream key lives in the admin under Configuration, alongside the server setup options.

How Do You Connect OBS to Owncast?

The owncast OBS connection takes under a minute. OBS connects to Owncast like it connects to any custom RTMP destination — Owncast is compatible with any RTMP encoder, including OBS, Streamlabs, and Restream. In OBS, open Settings, go to Stream, and set Service to Custom. That is the whole trick; everything else is just filling in the two fields.

Server:    rtmp://yourserver/live
Stream Key: <your rotated stream key>

The full default server form is rtmp://yourserver:1935/live — owncast rtmp ingest runs on port 1935, and it is configurable under Configuration > Server Setup if you need something else. If your encoder has no separate key field, append the key to the URL instead: rtmp://yourserver:1935/live/<stream-key>. Start streaming in OBS and Owncast picks the feed up automatically; your channel page switches from offline to live on its own.

What Happens When You Go Live?

When you go live, your viewers do not see the stream instantly — expect a few seconds of latency, and understand that this is a feature, not a bug. Owncast chops your feed into small HLS segments so playback stays smooth on every device and connection; those segments take time to generate and buffer, which is the latency-buffer tradeoff. Shorter buffers mean snappier chat-to-video sync but more stuttering on weak connections; longer buffers mean smoother playback with more delay. Do not fight the delay by staring at your own stream while you broadcast — watch your OBS preview and read the chat, and let the buffer do its job.

How Does Owncast Chat Work, and How Do You Moderate It?

Owncast ships with a built-in real-time owncast chat next to the video player — there is no third-party chat widget to embed and no external service to configure. By default there are no moderators, so step one is appointing yourself (and anyone you trust) from the admin. Moderation happens in two places: right in the chat, and in the admin under the Chat > Messages and Users pages. Moderators can remove single messages or ban users entirely; banning automatically blocks the user's known IP address, and there is also a Delete user action for permanent removal. On the prevention side, the chat settings let you set forbidden usernames, run spam and slur filters, and — since v0.2.5 — require chat authentication before anyone can post. Custom emoji are supported too, so your chat can have its own culture instead of default smileys.

How Do You Make Your Owncast Look Like Yours?

Your channel page is yours to brand, and the Appearance section of the admin is where it happens. Set the channel name, description, and social links first — these are what a first-time viewer reads. Then upload your logo and favicon (the favicon became changeable in v0.2.5), and add custom CSS to reshape the page beyond the defaults; custom JavaScript is supported as well if you need behavior changes. If you already have a website, you do not have to send people to your Owncast server at all: the stream embeds in any page through a standard iframe, so your channel can live inside your existing site design.

Should You Federate Your Stream? The Federation Question

Owncast federation is opt-in, not on by default — and that is a deliberate design choice, so treat it as a decision, not a setup step you missed. Owncast speaks ActivityPub, which means your channel can exist in the Fediverse: the owner has to explicitly enable each optional social feature before anything federates. Once enabled, a viewer with any Fediverse account (Mastodon and friends) can follow your channel, and following is how they get go-live notifications in their home feed. The Owncast directory (owncast.directory) is a separate opt-in: enable the "Enable directory" toggle in the admin and your server registers itself by pinging the directory while you are live. The social loop closes in the nicest way possible — favourites and boosts of your go-live post from the Fediverse show up directly in your stream chat, so your social audience and your viewers are the same room. Own your audience, said once: because follows and notifications run on open protocols at your own domain, no platform can take your subscriber list away when its algorithm changes.

One v0.3.0 feature belongs in this section: Featured Streams lets you feature other Owncast streams on your page. It works over ActivityPub and requires the other server to accept your feature request — a small, consensual version of the raid culture other platforms built.

Owncast vs PeerTube: Which Lane Are You In?

Beginners often confuse the two because both are self-hosted and both are federated, so here is the draw-the-line, said once: they are different products for different jobs, never rivals. Owncast is for live streaming — one broadcaster, one live feed, right now, with chat. PeerTube is for recorded video — a video library people browse and watch on demand, federated across instances. If your content is "I am live every Friday," you want Owncast; our PeerTube beginner guide covers the recorded-video lane. And if the Fediverse part of this guide intrigued you more than the streaming part, our GoToSocial beginner guide covers the microblogging lane — a different lane entirely, never a rival.

How Do You Put HTTPS on Owncast?

Owncast serves its web interface on port 8080 by default, which means your viewers' URLs look like http://yourserver:8080 — no padlock, and browsers will warn about the page. The standard fix is a reverse proxy in front of it that terminates TLS and forwards to port 8080, which also drops the :8080 from your URLs so your channel lives at a clean https://live.yourdomain.com. Open both ports in your firewall or security group (8080 for the web interface, 1935 for RTMP ingest), point your domain at the server, and put the proxy in front. The simplest path is covered in our Caddy beginner guide — Caddy fetches and renews the certificate for you, so the whole HTTPS lane is a few lines of config.

How Do You Back Up Owncast?

The data-is-files lesson, said once: everything Owncast knows lives in its data/ directory — the SQLite database at data/owncast.db (configuration, users, chat history), logs, custom emoji, and HLS segments. Owncast also writes periodic backups of its server data into a backup directory on its own (hourly database backups have been a feature since early releases), and there are CLI flags for the paranoid: --backupdir, --restoreDatabase, --database, and --logdir. If you run the Docker image, persistence is the /app/data volume — back up the host directory you mounted before any upgrade or config change, and you can restore the whole server by mounting it into a fresh container.

# back up the whole server: config, database, chat, emoji
rsync -a /path/to/owncast-data/ /backups/owncast-$(date +%F)/

Beginner Mistakes That Break an Owncast Setup

Almost every broken first stream traces back to one of these. Check the table before you announce your go-live.

Sources

Every fact in this guide was verified against a page fetched on November 1, 2026: the official Owncast installation quickstart (owncast.online/quickstart/installation), the Owncast releases page (owncast.online/releases, v0.3.0 September 3, 2026), the broadcasting documentation (owncast.online/docs/broadcasting), the chat moderation documentation (owncast.online/docs/chat/moderation), the directory documentation (owncast.online/docs/directory), the embed documentation (owncast.online/docs/embed), the Fediverse Report interview with maintainer Gabe Kangas (fediversereport.com/fediverse-201-owncast), the Owncast GitHub repository README, the Hostinger Owncast VPS template documentation (updated August 14, 2026), the InMotion Hosting Owncast-versus-Twitch guide, and the Uma Technology Owncast setup articles.

Frequently Asked Questions

Is Owncast really free?

Yes. Owncast is free and open source — there is no license fee, no per-viewer charge, and no revenue cut. Your costs are the server it runs on (a small VPS) and its bandwidth, which is the standard tradeoff of self-hosting: you pay for infrastructure instead of paying a platform with a cut of your audience.

Can viewers watch without installing anything?

Yes. Viewers watch in a normal web browser — Owncast serves a built-in web player with chat, and there is nothing to download. Only the broadcaster needs streaming software like OBS.

Does Owncast work with encoders other than OBS?

Yes. Owncast accepts any RTMP-compatible encoder, including Streamlabs and Restream. Point the encoder at rtmp://yourserver/live, supply the stream key, and it works the same way.

Can more than one person stream on one Owncast server?

Not as separate channels — Owncast is single-user by design, with one broadcaster per server. v0.3.0 added user management in the admin, but the product remains a single-broadcaster server. Multiple people can co-host a stream through one OBS session, and the Featured Streams feature lets you showcase other Owncast servers on your page.

Is my stream listed in the Owncast directory automatically?

No. The directory is opt-in: you must enable the "Enable directory" toggle in the admin, and your server only registers while you are live. Federation as a whole is opt-in — nothing about your server is announced to the Fediverse until you enable each social feature yourself.