Quick answer: choose the official SillyTavern Launcher if you want the easiest supported setup on Windows, macOS, or Linux. Choose a manual Git install if you want a transparent folder you can update with Git. Use Docker only if you already understand containers, and use Termux for Android. Every method installs the front end; you still need a separate local or cloud model backend.
This guide was refreshed on August 10, 2026 from the official SillyTavern installation documentation, 1.18.0 release notes, and 90 days of anonymized search questions that led readers here. Those questions show that general installation, Windows, and Android/Termux are the recurring pain points, so the walkthrough below treats each as a separate path instead of pretending one command fits every device.
Quick answer: the easiest path by device
| Device |
Best default |
What you install first |
Difficulty |
| Windows 10/11 |
Official Launcher |
Git, then SillyTavern Launcher |
Easiest desktop path |
| macOS |
Launcher or manual Git |
Homebrew/Git; Node.js for manual install |
Easy to moderate |
| Linux |
Launcher or manual Git |
Git; Node.js for manual install |
Easy if you use a terminal |
| Android |
Termux from F-Droid or GitHub |
Termux, Git, Node.js LTS, Nano |
Moderate; phone limits apply |
| Existing container host |
Official Docker Compose file |
Docker and Git |
Advanced |
For most beginners, the sensible order is desktop Launcher first, manual Git second, Android only when mobile use is essential, and Docker only when container operations are already familiar. The current official release branch is the stable default. The staging branch moves much faster and the maintainers do not recommend it for casual use.
What SillyTavern is — and what it is not
SillyTavern is a locally installed interface for working with text-generation models, image engines, and text-to-speech tools. It organizes characters, prompts, chats, lorebooks, presets, and connections. It is not an AI model and does not generate replies by itself. A successful installation gives you a browser interface, usually at http://localhost:8000; the next job is connecting a compatible backend.
That distinction explains a common “the page opens but nothing answers” report. The server and interface can be healthy while the model connection is missing, misconfigured, out of credit, or offline. Treat installation and backend connection as two separate checkpoints.
As checked on August 10, 2026, the latest stable GitHub release is SillyTavern 1.18.0, published May 3, 2026. The release branch package declares Node.js 20 or newer. That corrects the older requirement in the former version of this guide. Use the current Node.js LTS release unless the official project states otherwise.
What changed in SillyTavern 1.18.0 for a fresh install
The current release is not just a new number. Its official release notes say configuration migration now happens inside the app or through a dedicated npm run init command, rather than a post-install script. The same release moved user-facing error pages and user.css from public/ to data/ for immutable setups. That makes an old “copy only the public folder” backup especially unreliable: protect the actual data and configuration paths used by your install.
Version 1.18.0 also added basic-auth rate limiting, stricter forwarded-IP controls, private-address checks against server-side request forgery, and session-cookie invalidation after a password change. Those improvements do not make an open port safe. The official remote-connections guide still says not to expose the server directly through port forwarding; use authenticated access through a VPN or secure tunnel instead.
Finally, the maintainers linked a security notice about the third-party “Bot Browser” extension in the 1.18.0 release. Treat extensions as executable code, install only what you have reviewed and need, and get the base install plus one backend working before adding any extension. A clean first run gives you a control point: if the browser opens, the connection test succeeds, and a basic message returns before extensions are added, later breakage is much easier to isolate.
What 4,013 search impressions reveal about installation friction
Our anonymized search data for this guide covered May 10 through August 7, 2026 and recorded 4,013 appearances in Google results. The 20 leading queries accounted for 1,499 impressions. Grouping those leading queries by intent shows where a generic one-page checklist falls short:
| Intent in the leading query set |
Impressions |
What this guide does differently |
| General installation or setup |
925 |
Separates installing the interface from connecting a model backend |
| Windows |
261 |
Gives both the official Launcher and manual Git paths |
| Android or Termux |
205 |
Uses the maintained Termux route and calls out phone limitations |
| Launcher |
57 |
Explains what the Launcher simplifies and what it does not provide |
| macOS |
51 |
Keeps the Launcher and terminal instructions distinct |
The practical conclusion is that “install SillyTavern” is really three decisions: choose a supported device path, choose Launcher versus manual Git, then choose a separate backend. Mixing those decisions is why users can reach the localhost interface and still believe the installation failed. The walkthrough below deliberately verifies each layer before moving to the next.
Prerequisites and supported platforms
| Platform |
Required before manual install |
Start command |
Important warning |
| Windows |
Node.js LTS (20+) and Git |
Start.bat |
Do not install in Program Files/System32 or run Start.bat as administrator |
| macOS |
Git and Node.js LTS (20+) |
./start.sh or bash start.sh |
Use a normal user-owned folder |
| Linux |
Git and Node.js LTS (20+) |
./start.sh or bash start.sh |
Install prerequisites with your distribution’s package method |
| Android |
Maintained Termux, then git nodejs-lts nano |
bash start.sh |
Do not use the obsolete Google Play build of Termux |
| Docker |
Docker, command-line familiarity, official Compose file |
docker compose up |
Do not expose port 8000 directly to the public internet |
You do not need a dedicated graphics card to install the interface. Hardware requirements for generating text locally belong to the model backend, not SillyTavern itself. A cloud API can run without local model hardware. A large local model can require substantial memory and storage. Decide which backend class you want before downloading gigabytes of models.
Launcher vs manual Git vs Docker
| Method |
Best for |
Main advantage |
Main trade-off |
| Official Launcher |
New Windows, macOS, and Linux users |
Guided install and management menu |
Adds a launcher layer around the project |
| Manual Git |
Users comfortable with a terminal |
Simple folder, visible branch, straightforward updates |
You manage Git and Node.js yourself |
| GitHub Desktop |
Windows users who prefer a graphical Git client |
No command-line Git required for cloning/pulling |
You still launch the local server from its folder |
| Docker Compose |
Container users and home-server operators |
Reproducible image and mounted data volumes |
Networking, permissions, volumes, and updates are more complex |
| Termux |
Android users |
Runs natively on the phone |
Mobile process, memory, battery, and storage constraints |
The Launcher is the easiest default, but manual Git is not a second-class install. The official docs provide both. Docker is not automatically “better” because it isolates software: on Windows the official Docker guide explicitly recommends the normal Windows route for most people because Docker Desktop, virtualization, and WSL add complexity.
How to install SillyTavern on Windows
Option A: official Launcher
- Press
Windows + R.
- Install Git with the official documented command:
cmd /c winget install -e --id Git.Git.
- Create or open a normal user-owned folder. Do not choose Program Files, System32, or another Windows-controlled location.
- Type
cmd in File Explorer’s address bar to open a command prompt in that folder.
- Run
git clone https://github.com/SillyTavern/SillyTavern-Launcher.git && cd SillyTavern-Launcher && start installer.bat.
- Follow the Launcher menu, install the release branch, and start SillyTavern.
Option B: manual Git install
- Install the latest Node.js LTS and Git for Windows.
- Create a folder you control, such as
C:\AI\.
- Open Command Prompt in that folder.
- Clone the stable branch:
git clone https://github.com/SillyTavern/SillyTavern -b release.
- Open the new SillyTavern folder and double-click
Start.bat. Do not run it as administrator.
- Wait while the startup script installs dependencies and opens the interface.
If Windows hides file extensions, Start.bat may appear as a file named “Start.” Keep the console window open while using SillyTavern; closing it stops the local server. Compare any changed command against the current official Windows installation page before running it.
How to install SillyTavern on macOS
The manual path is short once Git and Node.js are available:
- Open Terminal and install Git. The official Launcher instructions use Homebrew: install Homebrew from its official site, then run
brew install git.
- Install a current Node.js LTS release if you are doing the manual Git install.
- Clone the stable branch with
git clone https://github.com/SillyTavern/SillyTavern -b release.
- Enter the folder with
cd SillyTavern.
- Start it with
./start.sh or bash start.sh.
For the Launcher, clone https://github.com/SillyTavern/SillyTavern-Launcher.git, enter that folder, run chmod +x install.sh && ./install.sh, then use chmod +x launcher.sh && ./launcher.sh. If macOS blocks an action, verify that you downloaded the official repository rather than bypassing security warnings for an unknown copy. The current source of truth is the official Linux and macOS installation page.
How to install SillyTavern on Linux
Install Git and Node.js using the supported method for your distribution. Then run:
git clone https://github.com/SillyTavern/SillyTavern -b release
cd SillyTavern
./start.sh
If the script is not executable, use bash start.sh. The official Linux Launcher path is also available: clone the Launcher repository, enter it, run chmod +x install.sh && ./install.sh, and then chmod +x launcher.sh && ./launcher.sh.
Avoid switching to root merely to make the app start. A normal user-owned directory keeps updates, backups, and plugin files easier to understand. Permission errors usually mean the folder ownership or execution bit needs attention, not that the whole application should run with unrestricted privileges.
How to install SillyTavern on Android with Termux
The official Android route is Termux. The project warns against the old Google Play version because it is no longer maintained. Install Termux from F-Droid or the official Termux GitHub releases, then:
termux-change-repo
pkg update && pkg upgrade
pkg install git nodejs-lts nano
git clone https://github.com/SillyTavern/SillyTavern -b release
cd ~/SillyTavern
bash start.sh
Open the local address shown in Termux in your Android browser. To update later, the official Android guide uses:
cd ~/SillyTavern
git pull --rebase --autostash
On a 32-bit Android device, the documented “Unsupported platform: android arm LEtime-web” fix is to install esbuild with pkg install esbuild. Android can run the interface, but the phone still has mobile limits. Keep a backup before changing performance or storage settings, and do not assume a phone can run the same local model as a desktop GPU.
Docker installation
Use Docker only if terms such as image, container, volume, port mapping, and Compose already make sense. The official prebuilt image is the quickest Docker route. Download the release branch’s official docker-compose.yml, open a terminal in that directory, and run:
docker compose up
The default public port is 8000. The official Compose setup creates persistent volumes for configuration and user data. Confirm those mappings before relying on the container, because deleting a container without persistent data is not a backup strategy. Never publish port 8000 to the open internet without a separate, properly secured access layer.
First launch and localhost checklist
- The terminal or console stays open without a fatal error.
- Your browser loads
http://localhost:8000 or the exact local address printed by the server.
- The SillyTavern interface appears and settings open normally.
- You can identify whether you installed the release or staging branch.
- You know where your config and data are stored before importing valuable chats or characters.
- You have not exposed the local server directly to the public internet.
Standalone mode, the default, stores config.yaml and data/ inside the installation directory. The official npm package runs in global mode by default, with operating-system-specific data locations. That difference matters during backup: do not copy only the application folder until you know which mode you are using.
Connect a cloud API or local backend safely
| Backend class |
What it does |
What you supply |
Privacy/cost question |
| Cloud API |
Runs the model on a provider’s servers |
Provider account, API key, compatible model selection |
Read current retention, moderation, and billing terms |
| Local API |
Runs a model through software on your device |
Backend such as Ollama or KoboldCpp, model files, sufficient hardware |
Local control is higher; hardware and setup burden are yours |
| Volunteer/shared service |
Routes generation through available workers |
Service configuration and patience for variable capacity |
Availability and data path differ from a fully local model |
In SillyTavern, open API Connections, select the connection type that matches the backend documentation, enter the endpoint and credential in the intended fields, and run the connection test before importing a complicated preset. “Chat Completion” and “Text Completion” describe prompt formats, not simply cloud versus local.
Never paste an API key into a character card, chat message, public screenshot, forum post, or shared preset. Do not commit credential or secret files to a public Git repository. A local front end does not make a cloud model local: messages sent to a cloud API leave your machine under that provider’s current terms.
A practical backend decision before you install models
Start with the smallest complete path, not the most ambitious one. If your desktop does not already run local models comfortably, connect a supported cloud API first and prove that the SillyTavern interface, character, preset, and connection all work together. That gives you a known-good front end. You can then introduce a local backend as a separate change instead of debugging installation, model loading, networking, and prompt formatting at the same time.
If local processing is the goal, pick the backend before downloading a model. Confirm which model format it supports, how much memory the chosen model needs, which local endpoint it exposes, and whether that endpoint is reachable from the same device as SillyTavern. Docker users need to remember that localhost inside one container does not automatically mean the host or another container. Android users should separate “running the SillyTavern interface in Termux” from “running a large language model on the phone”; those are very different hardware workloads.
When the test connection succeeds, create one disposable character and send one ordinary message. Check the server console for the outgoing request and response without sharing the log publicly. Only after that baseline works should you import valuable chats, large character collections, third-party extensions, or complex presets. This sequence is deliberately conservative, but it makes failures attributable: if the interface launches, the connection test passes, and a basic message returns, later problems belong to the customization layer rather than the installation.
Common installation errors and fixes
| Symptom |
Likely cause |
Smallest safe fix |
node is not recognized or version is below 20 |
Node.js missing, old, or absent from PATH |
Install the current Node.js LTS, reopen the terminal, check node --version |
| Windows permission or write errors |
Install is in a protected folder or started as administrator |
Move to a normal user-owned folder and run Start.bat normally |
| Browser does not open |
Server is still installing, stopped, or port differs |
Read the console; open the exact localhost URL it prints |
| Interface opens but replies fail |
No backend, wrong connection type, invalid endpoint/key, or offline model |
Configure and test one backend before changing prompts |
Cannot find module |
New or incomplete Node dependencies |
Run npm install; the official start scripts also install requirements |
git pull reports conflicts |
Tracked application files were modified locally |
Back up first; move custom changes out or use the official update guidance |
| Android reports unsupported arm LEtime-web |
32-bit Android dependency gap |
Run pkg install esbuild |
| Docker data disappears after recreation |
Missing or wrong persistent volume mapping |
Stop and verify config/data volumes before further container changes |
Change one variable at a time. Reinstalling repeatedly can hide the original error and destroy useful logs. Save the console message, verify the current official docs for your platform, and solve the first failing prerequisite before adding extensions or custom models.
Update, backup, and rollback
Before an update, stop the server and copy the data and configuration paths that match your mode. For a standalone install, protect at least data/ and config.yaml; if you use server-wide extensions, include their documented directory. For Docker, protect the host directories or named volumes mapped to config and data.
On Linux, macOS, or Termux, the basic official Git update flow is cd SillyTavern, git pull, then ./start.sh or bash start.sh. On Windows, try UpdateAndStart.bat; a Git install can also be pulled from a command prompt in the SillyTavern folder or through GitHub Desktop.
A rollback is not “download the old zip over the new folder.” Keep a dated copy of user data and config, record the working release/tag, and restore into a clean compatible installation if the update fails. Do not copy an entire old public/ directory over a newer version; the official update guide warns this can remove new application files and break features.
Privacy, local storage, and API-key handling
Local installation gives you control over the interface and local files. It does not guarantee that every connected service is private. A local model backend can keep generation on your hardware; a cloud API receives the prompts sent to it. Extensions and server plugins are additional code and should be reviewed before installation.
- Use a unique API key with the least access the provider supports.
- Keep SillyTavern bound to local access unless you deliberately configure a secured remote connection.
- Back up chats and characters to encrypted storage if they contain sensitive material.
- Review third-party extensions separately from the core project.
- Never share logs until you have checked them for prompts, local paths, tokens, and keys.
When a hosted companion is simpler
SillyTavern is the better fit when choosing models, prompts, characters, and storage is part of the appeal. If you mainly want to open a browser and chat without maintaining Node.js, Git, a backend, and backups, a hosted service may be simpler. The existing options on this page remain Candy AI, Girlfriend GPT, and Joi AI.
For the adult configuration layer after the base install works, continue with the SillyTavern NSFW setup guide. The installation and backend should be stable before you tune character cards, prompts, extensions, or generation settings.
FAQ
These questions come from the recurring Windows, Android/Termux, Launcher, Node.js, branch, and first-response searches in the same 90-day query set used above. Answers were checked against the official platform pages and 1.18.0 release notes linked in this guide.
What is the best way to install SillyTavern in 2026?
Use the official Launcher for the easiest supported desktop setup. Use manual Git when you want a simple, inspectable installation folder and easy git pull updates. The release branch is the stable default.
How do I install SillyTavern on Windows?
Install through the official Launcher, or install Node.js LTS and Git, clone the release branch into a normal user-owned folder, and run Start.bat without administrator permissions.
Can I run SillyTavern on Android?
Yes. The official route uses a maintained Termux build from F-Droid or GitHub, then Git and Node.js LTS inside Termux. Avoid the obsolete Google Play build of Termux.
What Node.js version does SillyTavern need?
The release branch package checked on August 3, 2026 declares Node.js 20 or newer. The official Windows guide recommends the latest LTS release.
Why does SillyTavern open but not generate a reply?
SillyTavern is the front end, not the model. Connect and test one compatible cloud or local backend in API Connections. Verify the connection type, endpoint, model availability, and key separately.
Should a beginner install SillyTavern with Docker?
Usually not. Docker is appropriate when you already understand containers, volumes, networking, and permissions. The Launcher or manual Git path has fewer moving parts for a first desktop install.
Is the release or staging branch better?
Release is recommended for most users and receives stable major releases. Staging changes several times a day and can break, so it is for enthusiasts who accept that risk.
Where are SillyTavern chats and settings stored?
In default standalone mode, configuration and data live in the installation directory. Global-mode paths differ by operating system. Confirm the mode and paths on your own installation before creating a backup.
Is SillyTavern free, and what can still cost money?
SillyTavern itself is free and open source. A cloud model provider may charge for API usage, while a local backend uses your own hardware, storage, and electricity. There is no single reliable “SillyTavern subscription price,” so check the current terms of the backend you choose instead of relying on an old fixed-price claim.
Verdict
The cleanest 2026 setup is boring on purpose: use the release branch, install in a user-owned folder, start with the Launcher or manual Git, confirm localhost works, connect one backend, and back up the correct data path before customization. The important corrections are Node.js 20+, maintained Termux outside Google Play, and the fact that Docker is an advanced option rather than the universal default.
If managing that stack sounds worthwhile, SillyTavern offers much more control than a one-click chat app. If it sounds like maintenance you do not want, the current hosted alternatives remain Candy AI, Girlfriend GPT, or Joi AI.
