← back to blog

how to run multiple Lemmy accounts across instances in 2026

how to run multiple Lemmy accounts across instances in 2026

running multiple Lemmy accounts is a different problem from running multiple Reddit or Twitter accounts because Lemmy is federated. each Lemmy instance is operated independently, with its own moderators, its own community policies, and its own user database. accounts on lemmy.world are different accounts from those on lemmy.ml or beehaw.org, even though they can interact across the federation.

multi-account operators on Lemmy face a unique combination: instance-level moderation rules, federation-level reputation effects, and the standard device-and-IP signals that any platform uses. the bar for passing all three is higher than on most non-federated platforms.

this guide covers what Lemmy instances actually check, why the common shortcuts fail, and the cloud phone workflow that holds up across the fediverse.

the federation context

Lemmy as software is open source. anyone can spin up an instance. the major instances at the time of writing include lemmy.world, lemmy.ml, beehaw.org, sh.itjust.works, and many smaller ones serving specific languages or topic communities. each instance has its own admins and its own rules.

federation means that an account on lemmy.world can post to a community on lemmy.ml and that post is visible to users on both instances. but the account itself lives only on lemmy.world. moderation actions taken by lemmy.world admins affect the account; actions by lemmy.ml admins affect only what is visible from lemmy.ml’s side.

multi-account on Lemmy can mean two things:

1. multiple accounts on the same instance. subject to that instance’s policies, often discouraged or banned outright.
2. multiple accounts across instances. generally tolerated as long as each instance’s individual rules are followed and the accounts do not federation-game (cross-vote, brigade, spam).

why Lemmy instances detect multi-accounting

instance admins use a mix of signals depending on the technical sophistication of the instance:

device fingerprint. the Lemmy web interface and clients send fingerprint data. shared fingerprints across accounts on one instance cluster them.

IP address and ASN. registration IP and login IPs are recorded. repeated overlap across accounts on the same instance triggers admin attention.

email and signup patterns. instances often record signup metadata closely. similar email patterns or sequential signups from the same IP cluster accounts.

voting and engagement graph. even across federation, vote patterns are visible. accounts that primarily upvote each other, especially when registered close in time, get flagged.

posting style and content overlap. instance moderators read posts. accounts publishing identical or near-identical content get noticed manually, faster than algorithmic detection on bigger platforms.

why common workarounds fail

multiple accounts on the same instance from one VPN. instance admins see the IP overlap and the timing. cluster.

switching accounts in the same browser. cookie clearing does not reset device fingerprint. instance admins with logging access see the device-fingerprint repeat.

registering 5 accounts on the same instance in 10 minutes. signup pattern itself is a signal. admins reject in batches.

the right approach: one cloud phone per Lemmy account, ideally one account per instance

the setup that survives:

1. one dedicated cloud phone per Lemmy account
2. each cloud phone on a real mobile carrier IP
3. ideally one account per instance you operate on, not multiple per instance
4. distinct posting style and voice per account
5. no cross-voting between your own accounts, even across instances

federation makes the second point critical. if you want to operate across the Lemmy fediverse with multiple identities, spread them across instances rather than concentrating on one. lemmy.world is large enough that some operators run two accounts there, but you should be conscious of the higher detection risk on a single instance.

cloud phones solve the device and IP layer in a way that browser tools alone cannot.

for a deeper comparison of cloud phone tools, see cloudf.one vs Geelark.

step-by-step: setting up multiple Lemmy accounts

step 1: provision one cloud phone per account

real mobile SIM per phone. note IP and device per account.

step 2: choose your instances

if you want 3 Lemmy identities, spread them across 3 instances rather than concentrating on one. respect each instance’s policies on multi-account.

step 3: register each account from its assigned phone

use the cloud phone’s mobile browser to register on the chosen instance. fresh email per account.

step 4: read each instance’s rules carefully

instance rules vary widely. lemmy.world is generally permissive. beehaw.org is more curated and explicitly discourages multi-account on the same instance. ml is politically curated. sh.itjust.works has its own culture. follow the rules of the instance you are on.

step 5: behave like a real user on each account

read the local feed, vote on posts you actually find interesting, comment on posts that warrant comments. accounts that post but never engage stand out.

step 6: do not cross-vote across your own accounts

even across instances, vote graphs are visible. cross-voting between your own accounts is the easiest pattern to detect and the fastest path to instance bans.

the federation reputation question

Lemmy has an emerging concept of cross-instance reputation. accounts that get banned from one major instance often face suspicion when they post from another. instance admins talk to each other, especially the admins of the larger instances.

the implication for multi-account operators: even if your accounts are technically isolated, behavior that gets one of them banned can make the others suspect. behavioral hygiene matters more in a federated context than in a closed platform.

the Lemmy documentation explains the federation model in more detail.

behavioral hygiene

what signals a real federated user:

• engagement spread across many users on each instance
• voting patterns that include downvotes (real users disagree sometimes)
• posting style that fits the local culture of each instance
• a mix of posting and reading time that looks human

what signals an operator:

• accounts that only engage with each other
• voting that is exclusively positive
• identical posting style across accounts
• registering many accounts in a short window

try a cloud phone for Lemmy multi-account

if you operate on the Lemmy fediverse and want multiple accounts that survive instance-level moderation, real device and real mobile carrier IP isolation per account is the foundation.

cloudf.one provides cloud phones with real SIMs accessible through a browser dashboard. each phone is a real device, on a real mobile carrier IP, permanently assigned to one Lemmy account. you can start a free trial and confirm the setup before scaling.

we cover the broader multi-account framework in how to run multiple TikTok accounts from Singapore.

frequently asked questions

does Lemmy as software prevent multi-accounting?

no, the software allows multiple accounts. multi-account policies are set at the instance level by admins.

can I run multiple accounts on lemmy.world specifically?

lemmy.world’s policies have evolved. as of 2026, multi-account is tolerated within reason but flagrant operators (vote brigades, spam, cross-engagement) get banned. read the current rules before assuming.

will my accounts on different instances be linked through federation?

instance admins do not have direct visibility into other instances’ user lists. but vote graphs and posting patterns visible across federation can lead admins to suspect linkage if the patterns are obvious.

is Lemmy stricter than Reddit on multi-account?

depends on the instance. some Lemmy instances are stricter than Reddit because admins are more hands-on. others are more permissive because the moderation surface is smaller and the platform is younger.

what about Mastodon and other Fediverse platforms?

similar principles apply. each instance has its own rules. Mastodon’s culture is generally less tolerant of obvious multi-accounting than Lemmy’s, with more focus on authentic single-identity participation. cloud phones still solve the device and IP layer in either case.