Getting Started with Mastodon

If you’ve heard “just leave Twitter/X and go to Mastodon” and had no idea what that actually meant, this guide is for you. It won’t assume you know what federation is, what an instance is, or why any of this matters more than just picking a new app.

The short version of why it matters comes down to a single distinction:

On a corporate platform, you’re renting your presence. On Mastodon, you can own it.

What that actually changes in practice is the subject of the companion piece, Owning the Terms: What Self-Hosting Actually Changes. This guide is the how. That one’s the why.

By the end of this, you’ll know what Mastodon is, how to pick an instance and get set up, and what it would take if you ever wanted to run your own.

What is Mastodon

Mastodon isn’t a single website — it’s software that anyone can run, and thousands of people and organizations do. Each installation is called an instance (or server), and instances talk to each other over a shared protocol. The result is a network of independently-run servers that function like one connected social network. This whole interconnected system is often called the fediverse.

The easiest way to picture this is email. You might have a Gmail address, a friend might use Proton, someone else runs their own mail server — and none of that stops you from emailing each other. Mastodon works the same way: you pick a server, get an address that looks something like @you@instance.social, and from there you can follow and be followed by people on any other instance, not just your own.

Nobody “owns” email. Mastodon works on the same principle.

This is fundamentally different from how Twitter/X, Instagram, or Threads work. There:

One company owns the whole network.
One company’s algorithm decides what you see.
One company sells ads against your attention.
One company can change the rules, the pricing, or your access, unilaterally, at any time.

On Mastodon, no single entity controls the network. Each instance sets its own rules and is moderated by its own admins, but no instance can dictate terms to the others. There’s no centralized algorithm — your timeline is, by default, just posts from people you follow, in order, full stop.

How to join an instance

Picking an instance

The instance you join is mostly a matter of community and moderation style, not a permanent technical commitment (more on that below — you can move later). A few things worth weighing:

Topic or community fit. Many instances are organized around a shared interest, profession, region, or identity — tech, art, science, specific cities, queer community spaces, and so on. Joining one that matches your interests puts you in a local timeline full of relevant posts from day one.
Moderation approach. Every instance publishes its own rules and moderation policy. Skim them before joining. An instance with clear, enforced rules against harassment tends to be a better experience than one with none.
Size. Bigger instances have more local activity but can be slower to moderate. Smaller instances are often tighter-knit and more responsive, but with less going on locally. Neither is objectively better — it’s a preference.
Trust and transparency. Look for instances that are upfront about who runs them, how they’re funded, and what happens to your data.

If you’d rather not overthink it, joinmastodon.org’s server picker lets you filter by language and general topic, and generalist instances (open to any topic) are a perfectly fine default if nothing else jumps out.

Signing up

Go to your chosen instance’s website (e.g. mastodon.social, or whichever one you picked).
Click the sign-up button and fill in a username, email, and password. Some instances have open registration; others ask a short application question to keep out spam — that’s normal, not a red flag.
Confirm your email.
You’re in.

First things to do

Fill out your profile. A bio, a profile picture, and (if relevant) your pronouns go a long way toward helping people decide to follow you.
Follow some hashtags. Hashtags work across the whole fediverse, not just your instance, and they’re one of the fastest ways to find people posting about things you care about. Search for a tag and hit follow — it’ll behave like a mini-timeline.
Find people. Many instances have a directory of local users. There are also several tools built specifically for migrating your social graph — see below.
Check the local and federated timelines. “Local” shows posts from people on your instance; “federated” shows a wider (and often overwhelming) slice of everything your instance can see across the network. Most people end up living mostly in their “Home” timeline (people they follow) once it’s populated.

Moving instances later

One advantage worth knowing about upfront: Mastodon supports account migration. If you outgrow your instance, or its admin steps down, or you just want to move, you can set up a redirect and move your followers to a new account on a different instance without starting from zero. It’s not instantaneous or perfectly seamless — you’ll need to re-follow the people you follow, and pending direct messages don’t move — but the follower relationship itself transfers. That portability is the thing corporate platforms don’t offer, and it’s part of what makes “instance choice” lower-stakes than it might first appear. Details are in Mastodon’s official migration guide.

How to self-host

This section is a stretch tier. Most people never need to do this, and that’s completely fine — joining an existing instance gets you full access to the network either way. Self-hosting is for people who specifically want control over their own server: custom moderation policy, a vanity domain, guaranteed uptime independent of anyone else’s decisions, or just the satisfaction of running your own infrastructure.

Who it’s for: people comfortable with (or willing to learn) basic server administration, who want long-term control over their presence, and who are willing to be the sole moderator and sysadmin of their own little instance — even a single-user one.

The realistic options

Managed hosting. Services like masto.host run the server for you — you get your own domain and full admin control over your instance’s rules and members, without touching a Linux box yourself. This is the middle ground: real ownership of your instance, without the ops burden. Pricing scales with user count and storage, and it’s the option worth trying first if self-hosting appeals to you.

DIY on your own server. Running Mastodon yourself means provisioning a VPS or dedicated server and managing the full stack. At a high level, that involves:

A domain name, pointed at your server.
A server with enough RAM and storage for your expected usage (Mastodon’s official docs list current minimums).
Installing and configuring the required services — a PostgreSQL database, Redis, and object storage for media, typically behind a reverse proxy.
Keeping the software updated as new Mastodon releases ship, including database migrations.
Backups — for the database and for media storage.
Being the moderator. Even a single-user instance still needs someone watching for spam, abuse reports from federated instances, and defederation decisions.

None of this is exotic if you’ve run other self-hosted services before, but it is ongoing responsibility, not a one-time setup. The official Mastodon server installation guide is the authoritative source for current requirements and steps, and it’s worth reading in full before committing — it’ll give you a much more accurate sense of the time investment than any summary can.

Where to start

If all of this feels like a lot: it isn’t, for the first step. The entire on-ramp is picking an instance and making an account — that’s it. Everything else, from hashtag-following to self-hosting, can wait.

That’s the whole point of owning your presence instead of renting it: you get to make these decisions on your own timeline, not someone else’s terms of service. If you want the fuller argument for why that distinction matters, Owning the Terms: What Self-Hosting Actually Changes goes deeper.