SillyTavern alternatives · verified August 2026

Every real way to run a tavern
on a phone — both families.

Ten options, one honest split. Family one packages the actual SillyTavern server into an app or a terminal — full desktop parity, and Android still gets a vote on background processes. Family two skips the server: native apps that read the same cards, lorebooks, and presets. We build Foreverse, one entry in family two, so weigh our judgment accordingly — every fact below is checked against each project's own releases and docs, with dates.

The split that matters

Do you need the real server, or just your files?

Everything about choosing a SillyTavern alternative collapses into this one question. The real server means every extension, every setting, byte-identical behavior — and a Node.js process a phone has to keep alive. Your files mean cards, lorebooks, presets, and regex in an app built for a phone — and a compatibility layer that is never quite 100%. Neither answer is wrong. Picking without knowing which one you need is.

Family one

Server packagers: Termux, ST-android, Wivern, ST-Ctrl

Four ways to run the genuine article. All four give you the real SillyTavern — extensions, vector storage, exact desktop behavior. All four are servers on a phone, which is the thing Android is built to suspend. Verified against each project's repository on 2026-08-12.

Family two

Native compatible apps: six real options

No Node process, no keepalive, updates from a store or a release page. The differentiator inside this family is format coverage — card spec versions, lorebook fidelity, regex, automation — and that is where the honest differences live. Disclosure again: Foreverse is ours.

Side by side

The whole field in one table

Status lines verified against each project's own repository, docs, or store listing on 2026-08-12. Projects this young change fast — treat release dates as the load-bearing column.

OptionWhat runsCardsST extensionsStatus (2026-08)
TermuxReal ST server, terminal-managedAll (it is ST)AllEvergreen; phantom-process babysitting
ST-androidReal ST server in an APKAll (it is ST)Install yes, updates brokenv0.5.0, 2026-07-29; ST 1.18.0
WivernFull ST fork in an APKAll (it is ST)IncludedLast release 2026-03-07; still ST 1.16.0
ST-CtrlReal ST server + manager consoleAll (it is ST)Manager: install/update/uninstallNew (2026-06); Chinese UI
ForeverseNative app, no serverv1/v2/v3 + charxNo runtime; built-in plugin centerGoogle Play and App Store
TavoNative app, no serverv1/v2/v3 + charxNoPlay + App Store; ~4.8 rating
PyreNative app, no serverv2 documentedNoAGPL; Android/Win/Linux/web
RPClientNative app, no serverv1/v2 (v2 export)NoOn F-Droid; active releases
WryTour AINative app, no serverv1/v2NoPlay + App Store; solo dev
MiniTavernNative app, no serverPNG/JSON + URL cardsNoPlay (SFW positioning); iOS listed

FAQ

The questions people actually ask

For the long-form version of the server-family story — exact Termux commands, the phantom-process workaround, VPS security switches — read the four-roads field guide. For what a native app covers and where it stops, the honest-limits section of the Foreverse tavern page is the shortest answer we have.

What is the best SillyTavern alternative on Android?

It depends on one question: do you need the actual SillyTavern server, or just your cards and lorebooks? If your setup leans on desktop extensions, pick an app that packages the real server — ST-android (updated July 2026, bundles SillyTavern 1.18.0) or ST-Ctrl (adds an extension manager and backup tools). If you want a phone-first app that survives screen locks with zero server, pick a native client that reads the same formats: Foreverse, Tavo, Pyre, or RPClient. There is no single best — there are two families, and mixing them up is how people end up disappointed.

Can I run SillyTavern on Android without Termux in 2026?

Yes, three projects now package the unmodified SillyTavern server plus a Node.js runtime inside an ordinary APK: ST-android (v0.5.0, July 2026, the most active), Wivern (a full fork including extensions, but its last release was March 2026 and still bundles the older SillyTavern 1.16.0), and ST-Ctrl (a Chinese-language shell from June 2026 with extension management and four performance modes). All three are one-tap installs — no terminal, no git. They are still servers living on a phone, so Android's process management still gets a vote in the background.

Is there an official SillyTavern mobile app?

No. SillyTavern ships as a Node.js server and the team distributes no mobile app — every project on this page is community-built or independent. That also means any app store listing trading on the SillyTavern name is a lookalike. The projects here are honest about what they are: ST-android and Wivern call themselves unaffiliated personal projects in their own READMEs.

Will my character cards, lorebooks, and presets work in a native alternative?

Cards yes, with version caveats. PNG and JSON cards are the ecosystem's common ground, but spec coverage differs: Foreverse and Tavo import chara_card_v3 including .charx archives; Pyre and RPClient document v1/v2 support. Lorebooks import broadly, though trigger fidelity (recursion, token budgets, decorators) varies by app. Presets and regex scripts are the least portable — test yours before committing. Server-family apps skip this whole question because they run the real thing.

What about iPhone — can I run any of this on iOS?

The server family is Android-only: iOS does not allow long-running server processes, so there is no Termux route and no ST-android equivalent. On iPhone you either open a cloud- or PC-hosted SillyTavern in Safari, or use a native client with an iOS build: Tavo and WryTour AI are on the App Store today, MiniTavern and NativeTavern have App Store listings, and Foreverse has been on the App Store since September 2026.

Are these community projects safe to install?

Most publish their source: ST-android, Wivern, and Pyre are AGPL-3.0, ST-Ctrl's shell is MIT, RPClient is on F-Droid, PocketTavern is source-available. The practical risks are elsewhere: several are single-maintainer projects that can go quiet (Wivern's last release was March 2026), sideloaded APKs skip store review, and anything holding your API keys deserves a look at where those keys are stored. Closed-source options like Foreverse and Tavo trade auditability for store distribution and faster product cycles — a real trade-off, not a footnote.

Formats are the exit door

Whichever family you pick, keep your files.

Cards as PNG/JSON, lorebooks as JSON, presets as files — every road on this page is reversible if you keep exports. If you want to see how far a native app gets with your actual library, Foreverse imports it in minutes; if it doesn't fit, your files leave with you. Related reading: the wider roleplay-app roundup and Foreverse vs SillyTavern in detail.