SillyTavern Setup Guide: The Honest Beginner Path
SillyTavern is where displaced roleplayers keep landing, and for good reason: your characters, your memory, your model, on your machine — nothing anyone can filter, adjust, or shut down. It's also the one setup in this category that asks real work of you. Here's the clean path, the order that avoids the usual disasters, and an honest read on whether you'll enjoy it.
By Ash Kepler · Jul 24, 2026 · 9 min read
Every migration wave in this category ends the same way: a portion of the refugees stop looking for a better platform and decide to stop having one. China's displaced users went this direction after the July shutdown. Chub's crypto-locked users are going now. And a steady share of Character.AI's 2026 exodus lands here too, for the same reason each time: SillyTavern is the only configuration where nobody can filter, adjust, or delete your characters.
It's also the one that asks real work of you. Here's the honest path.
What it actually is
SillyTavern is a free, open-source interface — installed on your machine, running a local server, opening in your browser. It gives you characters, prompts, memory tools, lorebooks, and the conversation UI. It does not give you the AI.
That's the part that surprises newcomers, so state it plainly: you bring your own model. Either a cloud API key (the practical route for most people — DeepSeek's pricing makes heavy use cost a few dollars a month) or a model running locally on your own hardware if you have the GPU for it.
The trade this creates is the whole point. A hosted app bundles model, account, characters, images, and interface into one product that someone else controls. SillyTavern splits them, hands you every piece, and asks you to assemble it. What you get back is a setup where the model doesn't silently change underneath you, the filter is whatever your model does and nothing more, and your character library is a folder on your own disk.
The install, in the order that works
Prerequisites first. Install Node.js 20 or newer and Git. Most first-run failures trace to an old Node version — if the terminal complains about Node when you try to start, that's your answer: update, close the terminal, open a fresh one, try again.
Get the project. Clone the official repository and use the release branch, not an experimental or staging branch. New users are drawn to the branch with newer features; new users are also the least equipped to debug a half-finished feature. Boring and stable for the first session.
Install to a simple folder path. Not a deeply nested one, not one with spaces or unusual characters, not inside a synced cloud drive. This prevents a whole family of errors that look mysterious and are just path problems.
Run the included start script, and leave the terminal window open — that's your local server. Closing it closes SillyTavern. The interface opens in your browser at a local address.
Desktop Windows or macOS is the easy path. Linux is equally fine if you're already there. Android via Termux works and is a troubleshooting project, not a beginner route — if mobile is your primary device, a hosted app will genuinely serve you better.
The first session: do less than you want to
This is the advice that separates people who stick with SillyTavern from people who bounce off it in an evening. The interface exposes an enormous number of controls at once — samplers, prompt structure, extensions, themes, expression packs — and the instinct is to explore them.
Don't. Your first session has four steps: connect one model, import one character card, have one short conversation, confirm it works. Nothing else. Extensions, visual novel mode, text-to-speech, custom themes, and prompt engineering all come after basic chat is proven, added one at a time so you know which change caused which effect.
Nearly every "SillyTavern is broken" complaint is actually five simultaneous configuration changes with no way to isolate the culprit.
Bringing your characters
If you're arriving from a platform that used PNG character cards, this is the easy part — SillyTavern imports them directly, definition intact. If you're arriving from a closed platform, you're pasting the definition text into the character fields instead, which works fine; the full export-and-import mechanics cover what travels and what doesn't.
One expectation to set now: conversation memory doesn't come with you, from anywhere, ever. The character arrives; the relationship restarts on top of it. Paste your relationship summary early and give it two or three weeks.
Once basic chat works, the feature that makes SillyTavern genuinely superior to hosted platforms for long-form work is lorebooks — keyword-triggered world information that injects only when relevant. That's the real payoff of this whole setup, and it has its own guide.
Who should actually do this
You should, if: you've lost characters to a shutdown or a policy change and never want to repeat it; you write long-form stories where memory management matters more than polish; you like tinkering; or you're paying a subscription that costs more than your API usage would.
You shouldn't, if: you primarily chat on a phone; you want images, voice, and a face bundled in (Candy does that well and no self-hosted setup competes on media); you want to start tonight without a project; or the phrase "keep the terminal open" made you tired.
There's no shame in the second list. The platform comparison has good hosted answers, and Janitor with your own API key is the honest middle path — most of the freedom, none of the installation.
The one-line version
Node 20, release branch, simple folder, one model, one character, one conversation — then stop and actually play for a week before touching anything else. The people who do it in that order tend to stay for years, because at the end of it they own something no announcement can take away. In a category where platforms die, pivot, and get regulated on someone else's schedule, that's worth an evening.
questions