SillyTavern on your phone: every route, honestly compared

Four real ways to get SillyTavern on a phone in 2026 — Termux on Android, a cloud VPS, LAN access to your PC, or a native tavern-style app. Costs, trade-offs, and what survives the migration.

A phone propped on a wooden tavern counter, its screen glowing with a warm chat interface

The question shows up in every community thread sooner or later: “can I run SillyTavern on my phone?” You can — four different ways, each with a very different bill attached. We have run all four: Termux installs on three Android devices, a VPS tavern that lived for a year, a NAS at home serving the LAN, and eventually a native app we built ourselves. Here is the honest ledger.

To try the native Foreverse workflow first, choose Android or iPhone, import one card, and check its greeting and lorebook. App Store availability depends on your account region. Keep the deployment comparison below for cases where you need the original SillyTavern environment.

Route 1: Termux on Android — the tinkerer's road

SillyTavern is a Node.js server, and Termux gives Android a Linux userland, so you can host the server on the phone itself and browse to localhost:8000. The official Termux installation guide gets you there in about five commands.

The catches arrive after the install. The Play Store build of Termux is unmaintained — you need F-Droid, which filters out half the audience on day one. Android's background killer loves nothing more than a long-running Node process, so a ten-minute screen lock can eat your session mid-scene. And every update is a git pull that may end in a merge conflict you get to resolve in nano, on a five-inch screen.

On an 8 GB flagship it runs fine. On a 4 GB midranger with a long chat and a heavy lorebook, it visibly chugs. If you enjoy the tinkering itself, this road gives you total control. If you just want to talk to your characters, keep reading.

Route 2: cloud hosting — one server workspace across devices

A hosted SillyTavern instance gives several devices access to the same server workspace through a browser. It can be useful when you need that original runtime, but it also adds maintenance and access-control work. Foreverse offers a separate native iPhone route for supported card-and-lorebook workflows; not every iPhone user needs a hosted server.

Three costs. Money: a usable VPS runs $3–6 a month. Ops: system updates, full disks, and the day a port scanner finds your weak password are all your problem. Trust: if you skip self-hosting and borrow someone's shared instance, your API keys and chat logs live on their machine. Plenty of people pretend not to think about that last one.

Route 3: your PC serves, your phone browses

If a computer at home stays on anyway, let SillyTavern listen on the LAN and point your phone at 192.168.x.x:8000. Zero extra cost, data never leaves the house. The obvious limit: it ends at your front door. Continuing last night's scene from a train means setting up Tailscale or another tunnel first — there goes another evening.

Route 4: a native app — deleting the deployment step entirely

Since 2025 a wave of natively built tavern-style apps has appeared: import your cards, plug in your own API keys, keep everything on-device — no Node.js, no Termux, no git pull. Foreverse is our entry in this lane: chara_card_v3 cards, lorebooks, regex scripts, Quick Reply automation, group chats, plus BYOK access to 60+ model providers with keys encrypted on the phone. It has Android and iPhone versions; the iPhone version reached the App Store in September 2026, outside mainland China. Check features against the version you will actually use rather than assuming perfect cross-platform parity. The roleplay page explains the workflow and supported assets.

A SillyTavern extension is not automatically a Foreverse plugin. Foreverse has its own plugin capabilities; verify your required behaviors on your target platform and keep original exports. Card import, preset compatibility, and chat-history migration are separate checks.

What Route 4 looks like in practice — card import and in-character chat on a phone, cued in the full demo. Real screen recording.

The comparison, in one table

RouteDifficultyMonthly costWhere data livesBest for
Termux localHigh (CLI)$0On deviceFlagship phones, tinkerers
Cloud VPSMedium (ops)$3–6Your serverMulti-device, stability first
LAN to PCMedium$0 (PC stays on)Your computerHomebodies
Native appLowFrom $0On deviceCommuters, no-ops people

Our actual recommendation

For card chat on a phone, start with one Foreverse import and a short conversation. Keep your original card and verify the lorebook behavior. A required original-runtime extension or an existing shared server workspace may justify another route; evaluate that concrete requirement rather than treating a popularity claim as a reason to deploy.

FAQ

Can SillyTavern run natively on an iPhone?

No. SillyTavern is a Node.js server application, and iOS does not allow long-running server processes. iPhone users have two realistic options: open a cloud- or PC-hosted instance in Safari, or use a natively built tavern-style app that reads the same character cards — Foreverse, for example, is on the App Store and reads chara_card_v3 PNG/JSON/.charx files and lorebooks.

Why does my Termux SillyTavern stop when the screen locks?

Android freezes background processes to reclaim memory, and a Node.js server inside Termux is a prime target. termux-wake-lock and disabling battery optimization help, but aggressive vendor ROMs often override both. It is a platform behavior, not a SillyTavern bug.

Will my character cards work across all four routes?

Yes — PNG and JSON character cards plus lorebook JSON files are portable everywhere. Chat history is stored as jsonl inside the SillyTavern ecosystem; native apps vary, so check that the app explicitly imports SillyTavern data before you commit.

Is a shared cloud tavern safe to use?

Only as safe as the person running it. On a shared instance, your API keys, cards, and chat logs all pass through someone else's server. Self-host if you can; if you cannot, treat any service that asks for your API key with appropriate suspicion.

Questions or ideas? Join our Discord →