autotok — TikTok Auto Uploader

Upload and schedule TikTok videos from the command line, Python, TypeScript or Go, with a proxy per account.

uv tool install autotok · npm install autotok · one login · one command per upload

_{Click the video to watch it with sound.}

---

Install

Command line and Python

uv tool install "autotok[youtube]"
autotok install-browser                                   # one-time browser download, about 300 MB

Then log in once per account, and upload with one command:

autotok login -n my_account                               # log in on the page that opens; the QR code is quickest
autotok upload -u my_account -v clip.mp4 -t "Hello #fyp"

No uv? pipx install "autotok[youtube]" or pip install "autotok[youtube]" work too. Getting started goes through each step, including proxies and cloud browsers.

TypeScript and JavaScript (Node.js)

npm install autotok
npx playwright install chromium                           # one-time browser download

import { login, uploadVideo } from "autotok";

await login("my_account");                                // once: log in on the page that opens
await uploadVideo("my_account", "clip.mp4", "Hello #fyp");

Typed, promise-based, no Python needed, and it shares saved accounts with the CLI. See the TypeScript SDK.

Go, or one binary with nothing else to install

go install github.com/makiisthenes/TiktokAutoUploader/go/cmd/autotok@latest

or download the autotok binary for your system from the releases (the go/v... ones). It has the same commands as above, needs no Python or Node.js, and uses the Chrome already on your computer. In Go code: go get github.com/makiisthenes/TiktokAutoUploader/go. See Go.

---

Sponsors

Proxy-Seller provides residential, ISP, datacenter IPv4/IPv6 and mobile proxies across 220+ locations. Built for web scraping, automation, multi-account management, GEO testing and other workflows that require reliable, flexible proxy infrastructure.

Get 15% off with code AUTO15 — Get proxies from Proxy-Seller →

RapidProxy provides 90M+ residential IPs across 195+ countries, with sticky and rotating sessions, HTTP(S)/SOCKS5 and high concurrency. Assign a separate session per account for cleaner IP isolation. Traffic never expires, with flexible geo-targeting and 99.99% uptime.

Get 10% off with code RAPID10 — Try RapidProxy →

Termius provides a secure, reliable, and collaborative SSH client.

Get Termius →

---

Getting started

Setup takes about five minutes. After installing (step 1), you can run autotok setup to be walked through the rest: it checks the browser, asks for a proxy and tests it, then logs you in to TikTok through it. The steps below do the same by hand.

1. Install autotok

uv tool install "autotok[youtube]"

That's it: autotok is now a command you can run from any terminal (check with autotok --version). uv keeps autotok separate from your other Python packages, and downloads Python for you if you don't have it.

Don't have uv? Install it with one line from docs.astral.sh/uv, or use pipx: pipx install "autotok[youtube]".

• Update later: uv tool upgrade autotok.
• Try it without installing: uvx --from "autotok[youtube]" autotok --version.
• Using autotok from Python code? Add it to your project: uv add "autotok[youtube]" or pip install "autotok[youtube]".
• Using TypeScript or JavaScript? npm install autotok instead, see the TypeScript SDK. From code, login() and uploadVideo() replace the commands in steps 3 and 4.
• Can't install Python, or writing Go? Use the single autotok binary from the releases instead: the steps below are the same. See Go.
• [youtube] adds YouTube-link support. Leave it out if you don't need it.
• autotok "not recognized" or "command not found"? Run uv tool update-shell once and open a new terminal.

2. Choose where the browser runs

autotok uses a browser for the one-time login and to sign each upload. Pick one:

Option	Best for	Setup
Local (default)	Your own computer	autotok install-browser, a one-time download of about 300 MB
Cloud (Browserbase or Steel)	Servers, Docker, or keeping your computer free	Add an API key to a settings file. See Cloud browsers

For the local browser on a fresh Linux server, run autotok install-browser --with-deps as root, which also installs Chromium's system libraries.

3. Log in to TikTok (once per account)

autotok login -n my_account

A browser window opens on TikTok's login page. Log in however you like; the QR code with the TikTok app on your phone is quickest. The window closes by itself and the session is saved as my_account. With a cloud browser you get a link to open instead.

autotok accounts check my_account     # confirms TikTok accepts the saved session

• Going to use a proxy for this account? Pass it now, so the login and later uploads share one IP: autotok login -n my_account -p http://user:pass@host:port (see Proxies).
• Repeat with a different -n name for each account.
• Sessions are saved in ~/.autotok/accounts. Treat them like passwords.

4. Upload

autotok upload -u my_account -v "C:\Videos\clip.mp4" -t "My caption #fyp"

That's it. More examples:

autotok upload -u my_account -v clip.mp4 -t "Just for me" -vi 1                 # private
autotok upload -u my_account -v clip.mp4 -t "Later #fyp" -sc 3600               # publish in 1 hour
autotok upload -u my_account -yt "https://www.youtube.com/shorts/xxxxxxxxxxx" -t "Caption"

-v takes a path to any video, or just a file name if the video is in ~/.autotok/videos. See the CLI reference for every option.

5. Optional: save your settings in a file

Settings such as a cloud browser or its API key go in a .env file. autotok looks in the folder you run it from, then in ~/.autotok/.env; the second location works from any folder. Copy .env.example (from this repository) or start with just what you need:

# ~/.autotok/.env   (Windows: C:\Users\<you>\.autotok\.env)
AUTOTOK_BROWSER=browserbase
BROWSERBASE_API_KEY=bb_live_...

Where next?

I want to...	See
Run several accounts, each with its own IP	Proxies
Avoid running a browser on my computer	Cloud browsers
Upload from Python code	Python SDK
Upload from TypeScript or JavaScript	TypeScript SDK
Upload from Go, or use one binary with no Python	Go
Let an AI agent (Claude, Cursor...) upload for me	MCP server
Run on a server or in a container	Docker
Use a web dashboard with a scheduler	Web app
Fix an error	Troubleshooting

---

Features

• One-command uploads through TikTok's web upload API. No clicking through the TikTok website.
• Proxy per account: login, request signing and every upload go through the same proxy, so each account always appears from one IP. HTTP(S) and SOCKS5 are supported.
• Multiple accounts: log in once per account and upload by name.
• Scheduling: TikTok-side scheduling from 15 minutes to 30 days ahead (TikTok limits some accounts to 10 days). The self-hosted web app adds a scheduler with no time limit.
• Post settings: public or private, and comments, duets, stitches and the AI-generated label on or off.
• Clickable hashtags and @mentions, emoji-safe.
• YouTube links download automatically with yt-dlp.
• Python SDK, CLI, and an optional web app (Docker) with a browser-based login.
• TypeScript SDK on npm (npm install autotok): fully typed, promise-based, no Python needed, and it shares saved accounts with the CLI.
• Go package and a single binary: go get the library, or download one autotok executable with no Python or Node.js. It shares saved accounts with the other packages.
• MCP server so AI agents (Claude, Cursor, VS Code...) can upload and schedule for you.
• Cloud browsers: run the login and signing browser on Browserbase or Steel (cloud or self-hosted) instead of your computer.
• Docker image for running the CLI on servers.
• No Node.js needed for the Python package: TikTok's request signatures are computed in headless Chromium.

---

Proxies

Running several accounts from one IP is the quickest way to get them flagged. autotok lets you give every account its own proxy, and uses it everywhere that account talks to TikTok:

Step	Goes through the account's proxy
Login browser (autotok login, web app login)	✅
Signature page fetch	✅ (the signing browser itself makes no network requests)
Upload API calls and video transfer	✅
YouTube downloads	❌ (not TikTok traffic; saves proxy bandwidth)

Set, change and test proxies

autotok setup asks for the proxy, tests it and logs in through it. To do it by hand:

autotok login -n alice -p http://user:[email protected]:7000   # set at login
autotok proxy set alice socks5://user:[email protected]:1080     # set or change later
autotok proxy test -u alice                                          # shows the IP TikTok will see
autotok proxy clear alice                                            # go direct
autotok accounts list                                                # every account and its proxy (passwords hidden)

autotok upload -u alice -v clip.mp4 -t "hi" -p http://other:pass@host:8000   # one-off override
autotok upload -u alice -v clip.mp4 -t "hi" --no-proxy                       # ignore the saved proxy once

Accepted formats (scheme defaults to http)

http://user:pass@host:port      https://user:pass@host:port
socks5://user:pass@host:port    host:port
user:pass@host:port             host:port:user:pass      ← the export format most providers use

Tips

• Use residential or mobile proxies, one per account, with a sticky session (same IP for hours). A proxy that rotates the IP on every request makes a logged-in session look hijacked.
• Log in through the proxy you will upload with (autotok login -p ...). Logging in from home and uploading from a proxy is a mismatch TikTok can see.
• Chromium can't use SOCKS5 proxies that need a username and password. For the login step, use your provider's HTTP endpoint (uploads work with either).
• Passwords are never printed: the CLI and web app show http://user:****@host:port.

Need proxies? See our sponsors.

---

Cloud browsers (Browserbase, Steel)

autotok needs a browser in two places: the one-time login, and signing each upload (TikTok's anti-bot signatures are computed in a browser page). By default that's Chromium on your machine. Set AUTOTOK_BROWSER to run it in the cloud instead. Nothing then needs to be installed or opened locally, which makes it a good fit for servers and Docker.

AUTOTOK_BROWSER	Where the browser runs	Settings
local (default)	Chromium on this machine	autotok install-browser once
browserbase	Browserbase	BROWSERBASE_API_KEY (optional BROWSERBASE_PROJECT_ID, BROWSERBASE_REGION)
steel	Steel Cloud, or your own steel-browser server	Cloud: STEEL_API_KEY. Self-hosted: STEEL_BASE_URL, e.g. http://localhost:3000

Put the settings in your .env file (copy .env.example):

AUTOTOK_BROWSER=browserbase
BROWSERBASE_API_KEY=bb_live_...

Then use autotok as usual:

autotok browser check                 # starts a session and shows the IP it browses from
autotok login -n alice -p http://user:[email protected]:7000
autotok upload -u alice -v clip.mp4 -t "Hello #fyp"

Or pick per command: autotok --browser steel login -n alice.

Logging in: autotok login prints a live-view link and opens it in your normal browser. Log in to TikTok in that page; the session is saved as soon as you're in and the cloud browser is closed.

Self-hosted Steel is free and open source:

docker run -p 3000:3000 -e DOMAIN=localhost:3000 ghcr.io/steel-dev/steel-browser

and in .env:

AUTOTOK_BROWSER=steel
STEEL_BASE_URL=http://localhost:3000

Set DOMAIN to the address you reach the server at. Without it, steel-browser tells browsers to connect to 0.0.0.0 and its live view stays blank, so you can't log in. autotok warns when it sees this. A self-hosted steel-browser runs one session at a time.

Good to know:

• Use an account proxy with cloud logins. The account's proxy is applied to the cloud login session, so TikTok sees the same IP at login and upload. Without one, TikTok sees the login come from the provider's IP and uploads come from yours.
• "Verify it's really you" after logging in means TikTok saw an unfamiliar device on a datacenter IP. You can complete it in the live view, but it's better to avoid it: use an account proxy, or on a paid Browserbase plan set BROWSERBASE_PROXY_COUNTRY=GB (your country) to log in through a home IP there. On the free plan, BROWSERBASE_REGION set to the region nearest you (e.g. eu-central-1) at least avoids a US login.
• The live view shows only the TikTok tab, so autotok closes popups such as "Continue with Google" during cloud logins. Use the QR code, email/username or phone instead.
• Browserbase only takes HTTP/HTTPS proxies, and custom proxies need its Developer plan or higher. Custom proxies on Steel Cloud may need a paid plan too.
• Only the browser runs in the cloud. The video file still goes from your machine (through the account proxy) straight to TikTok, so cloud usage stays small: one short session per login and per upload.
• Want another provider? Subclass autotok.browsers.CloudProvider and call autotok.browsers.register_provider("name", YourProvider).

---

Python SDK

import autotok

autotok.login("alice", proxy="http://user:[email protected]:7000")   # once; opens a browser

result = autotok.upload_video("alice", "clip.mp4", "Hello #fyp")
print(result.video_id)

# More control: reuse a client, set post options, schedule
from datetime import datetime, timedelta, timezone

client = autotok.Client.from_account("alice")          # uses alice's saved proxy
client.upload(
    "clip.mp4",
    "Going live tomorrow #fyp @friend",
    schedule=datetime.now(timezone.utc) + timedelta(days=1),   # or seconds, or a timedelta
    visibility="public",            # or "private"
    allow_comment=True,
    allow_duet=False,
    allow_stitch=False,
    ai_label=False,
)

# Errors are typed; `retryable` is True only when nothing reached TikTok's publish step.
try:
    client.upload("clip.mp4", "caption")
except autotok.PublishError as e:          # TikTok rejected the post (e.g. guidelines)
    print(e.status_code, e.status_msg)
except autotok.AutotokError as e:
    print("failed:", e, "safe to retry:", e.retryable)

Already have a sessionid cookie from your browser? Skip the login window:

autotok.import_session("alice", "<sessionid value>", datacenter="<tt-target-idc value>")

---

TypeScript SDK

The same uploader for TypeScript and JavaScript, on npm as autotok. It runs on Node.js 22.12+, has types included, and needs no Python. It reads and writes the same ~/.autotok/accounts, so an account you log in to with the CLI works from TypeScript too, and the other way round.

npm install autotok
npx playwright install chromium        # one-time browser download, unless you use a cloud browser

import { Client, login, uploadVideo, AutotokError, PublishError } from "autotok";

await login("alice", { proxy: "http://user:[email protected]:7000" });   // once; opens a browser

const result = await uploadVideo("alice", "clip.mp4", "Hello #fyp");
console.log(result.videoId);

// More control: reuse a client, set post options, schedule
const client = await Client.fromAccount("alice");        // uses alice's saved proxy
await client.upload("clip.mp4", "Going live tomorrow #fyp @friend", {
  schedule: new Date(Date.now() + 24 * 3_600_000),     // a Date, a timestamp in ms, or an ISO string
  visibility: "public",                                 // or "private"
  allowComment: true,
  allowDuet: false,
  allowStitch: false,
  aiLabel: false,
});

// Errors are typed; `retryable` is true only when nothing reached TikTok's publish step.
try {
  await client.upload("clip.mp4", "caption");
} catch (error) {
  if (error instanceof PublishError) console.log(error.statusCode, error.statusMsg);
  else if (error instanceof AutotokError) console.log("failed:", error.message, "safe to retry:", error.retryable);
}

• Everything in your editor is typed: options, results and every error class.
• The video can be a path, a file name in ~/.autotok/videos, or the video's bytes (Buffer/Uint8Array).
• Works from ES modules and CommonJS (require("autotok")), and with TypeScript's nodenext, node20 and bundler settings.
• Proxies, cloud browsers (AUTOTOK_BROWSER), the configuration variables and .env files work as described in this README; call loadEnv() to read .env.
• Already have a sessionid cookie? await importSession("alice", "<sessionid>", { datacenter: "<tt-target-idc>" }).

The full API is in js/README.md. The CLI, YouTube links, the MCP server and the web app are in the Python package.

---

Go SDK and single binary

autotok is also a Go module, which builds into one autotok binary with no Python or Node.js needed. The binary has the same commands and flags as the Python CLI. Like the TypeScript package, it reads and writes the same ~/.autotok/accounts, so accounts work everywhere.

go install github.com/makiisthenes/TiktokAutoUploader/go/cmd/autotok@latest   # or download a release binary
autotok login -n my_account
autotok upload -u my_account -v clip.mp4 -t "Hello #fyp"

It logs in and signs with the Chrome, Chromium or Edge already on your computer, or with Playwright's Chromium if the other packages installed it. On a machine with neither, run autotok install-browser, which downloads Chrome for Testing (about 200 MB, once).

From Go code (Go 1.26+):

import autotok "github.com/makiisthenes/TiktokAutoUploader/go"

ctx := context.Background()
if _, err := autotok.Login(ctx, "alice", &autotok.LoginOptions{Proxy: "http://user:[email protected]:7000"}); err != nil {
	log.Fatal(err) // once; opens a browser
}
client, err := autotok.NewClient("alice", nil) // uses alice's saved proxy
if err != nil {
	log.Fatal(err)
}
result, err := client.Upload(ctx, "clip.mp4", "Hello #fyp", &autotok.UploadOptions{
	Schedule: time.Now().Add(24 * time.Hour), // optional: 15 minutes to 30 days ahead
})
if err != nil {
	log.Fatal(err) // autotok.IsRetryable(err) says whether trying again is safe
}
fmt.Println(result.VideoID)

• Every call takes a context.Context, so uploads can be cancelled or given a deadline.
• Errors are typed (*autotok.PublishError, *autotok.UploadError...) for errors.As.
• Proxies and cloud browsers (AUTOTOK_BROWSER) work as described in this README. The login browser also works with SOCKS5 proxies that need a password.
• YouTube links work when yt-dlp is installed. The setup wizard, the shell and the MCP server are in the Python package only.

The full API is in go/README.md and on pkg.go.dev.

---

MCP server (AI agents)

autotok includes an MCP server, so AI agents such as Claude, Cursor or VS Code can upload and schedule videos for you. It uses the same saved accounts as the CLI.

uv tool install "autotok[youtube,mcp]"    # or: pip install "autotok[youtube,mcp]"

Claude Code

claude mcp add autotok -- autotok mcp

Claude Desktop, Cursor and other clients: add this to the client's MCP settings (claude_desktop_config.json, .cursor/mcp.json, ...):

{
  "mcpServers": {
    "autotok": { "command": "autotok", "args": ["mcp"] }
  }
}

If the client can't find autotok, use the full path that which autotok (Windows: where autotok) prints. Then ask, for example: "Upload clip.mp4 to my_account with the caption 'Hello #fyp', scheduled for 6 pm tomorrow."

Tool	What it does
list_accounts	Saved accounts, whether each is logged in, and its proxy (masked)
check_account	Asks TikTok whether an account's session still works
list_videos	Files in your videos folder
upload_video	Uploads a file or a YouTube link, posts now or schedules 15 minutes to 30 days ahead, with the same post settings as the CLI
login, login_status	Starts a login. You finish it in the browser window that opens (or at the link a cloud browser gives)
set_proxy, test_proxy	Saves or removes an account's proxy, and shows the IP TikTok will see

• Your sessions stay on your computer. The tools never return cookies, and proxy passwords are masked.
• Every upload is a real post. Most clients ask before each tool call; keep that on for upload_video. An upload error that says the post may or may not exist tells the agent not to retry, so nothing is posted twice.
• Timeouts don't cause duplicates. If a client gives up on a long upload and calls upload_video again with the same account, video and caption, it gets the first upload's result instead of a second post. Clients that support progress notifications keep waiting meanwhile.
• Streamable HTTP: autotok mcp --http serves http://127.0.0.1:8000/mcp (--host, --port to change). There is no authentication, so keep it on localhost or behind your own.

---

CLI reference

autotok setup                         # step by step: browser, proxy (tested), TikTok login
autotok login     -n NAME [-p PROXY] [--force] [--sessionid ID --datacenter DC]
autotok upload    -u NAME (-v FILE | -yt URL) -t CAPTION [options]
autotok accounts  list | check NAME | remove NAME
autotok proxy     set NAME PROXY | clear NAME | test [PROXY | -u NAME]
autotok show      -u (accounts) | -v (videos)
autotok browser check [-u NAME]       # test the local or cloud browser
autotok install-browser [--with-deps]
autotok shell                         # interactive prompt
autotok mcp [--http [--host H] [--port P]]   # MCP server for AI agents (needs autotok[mcp])

autotok --browser {local,browserbase,steel} <command> ...   # choose where the browser runs

Upload options:

Flag	Description	Default
-u / --user	Saved account name	required
-v / --video	Video file (path or name in your videos folder)	—
-yt / --youtube	YouTube URL to download and upload	—
-t / --title	Caption, up to 2200 characters	required
-sc / --schedule	Publish this many seconds from now (900–2592000; some accounts only allow up to 864000)	now
-vi / --visibility	0 public, 1 private	0
-ct / --comment	Allow comments (0/1)	1
-d / --duet	Allow duets (0/1)	0
-st / --stitch	Allow stitches (0/1)	0
-ai / --ailabel	Label as AI-generated (0/1)	0
-p / --proxy	Proxy for this upload only	account's proxy
--no-proxy	Ignore the account's saved proxy	—

python cli.py ... in this repository still works and is the same as autotok ....

---

Docker

The Dockerfile in the repository builds the CLI with Chromium included:

docker build -t autotok .

docker run --rm -it -v autotok-data:/data autotok accounts list
docker run --rm -it -v autotok-data:/data -v "$PWD/videos:/data/videos" \
  autotok upload -u alice -v clip.mp4 -t "Hello #fyp"

Saved accounts live in /data, so keep it in a volume. Containers have no screen, so log in with a cloud browser and open the link it prints:

docker run --rm -it -v autotok-data:/data \
  -e AUTOTOK_BROWSER=browserbase -e BROWSERBASE_API_KEY=bb_live_... \
  autotok login -n alice -p http://user:[email protected]:7000

You can also save a session cookie from your own browser with login --sessionid ... --datacenter ....

Using a cloud browser for everything? Build without the local Chromium for a much smaller image: docker build --build-arg INSTALL_BROWSER=false -t autotok:slim .

---

Web app (self-hosted)

A local control panel with accounts, proxies, a video library, uploads and a scheduler, plus a virtual browser for logging in. Requires Docker.

git clone https://github.com/makiisthenes/TiktokAutoUploader.git
cd TiktokAutoUploader
docker compose up --build

Open http://localhost:3000. The API docs are at http://localhost:8000/docs.

• Accounts: add accounts by logging in through the built-in virtual browser (with an optional proxy), then set, change or test each account's proxy and check its session.
• Upload: drop a file, pick one from the library, or paste a YouTube link. Publish now or schedule for any time.
• Schedules: the scheduler retries only failures that happened before anything reached TikTok, so a job can't post twice. A job that was cut off while publishing is marked may already be posted, and retrying it asks you to check TikTok first.

Data lives in ./data. To use an account you logged in to with the CLI, copy its file into the app's store and click Import from disk on the Accounts page:

mkdir -p data/autotok/accounts && cp ~/.autotok/accounts/my_account.json data/autotok/accounts/

(Files the containers write are owned by root on Linux, so use the web app's own login for accounts you manage there.)

To sign uploads with a cloud browser, put AUTOTOK_BROWSER and its settings (see Cloud browsers) in a .env file next to docker-compose.yml. Logging in through the web app still uses its built-in virtual browser.

Scripts that call the API directly must send the header X-Requested-With: autotok on POST/PATCH/DELETE requests. This stops other web pages from using the local API. The API also only answers to localhost and 127.0.0.1. If you reach the app by another name (say, behind your own reverse proxy), add it to .env: AUTOTOK_ALLOWED_HOSTS=tiktok.home.lan.

The web app has no login of its own and only listens on 127.0.0.1. Don't expose it to the internet.

---

Configuration

Everything is optional. Put settings in a .env file: copy .env.example to .env and fill in what you use. autotok reads .env from the folder you run it in, then ~/.autotok/.env. Variables already set in your environment take priority, and docker compose reads the same file. .env holds API keys, so never commit it (it's in .gitignore).

Variable	Purpose	Default
AUTOTOK_HOME	Saved accounts and settings	~/.autotok
AUTOTOK_VIDEOS_DIR	Videos folder and YouTube downloads	$AUTOTOK_HOME/videos
AUTOTOK_BROWSER	Where login/signing browsers run: local, browserbase, steel	local
AUTOTOK_BROWSER_CHANNEL	Use an installed browser, e.g. chrome	Playwright Chromium
AUTOTOK_BROWSER_PATH	Full path to a Chrome/Chromium binary	Playwright Chromium
BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID, BROWSERBASE_REGION, BROWSERBASE_PROXY_COUNTRY	Browserbase settings	—
STEEL_API_KEY, STEEL_BASE_URL, STEEL_CONNECT_URL	Steel settings (STEEL_BASE_URL for self-hosted)	Steel Cloud

Account files contain your TikTok session (equivalent to your password). They are saved with owner-only permissions; keep them private.

---

Upgrading from TiktokAutoUploader 1.x

• Install: follow Getting started (uv tool install "autotok[youtube]", then autotok install-browser). Node.js and npm install are no longer needed.
• Sessions: saved sessions in CookiesDir/ are migrated automatically the first time you use them from the repository folder. The flags are the same, and python cli.py still works.
• Scheduling: -sc schedules on TikTok's side again (15 minutes to 10 days). The 1.x local queue (cli.py schedule list|cancel) now lives in the web app's Schedules page.
• Bug fixes: privacy, comment, duet and stitch settings are now actually applied. Earlier versions always posted publicly with everything allowed. Hashtags are clickable again.
• Removed: config.txt and the unused ImageMagick video-editing helpers.

---

Troubleshooting

Problem	Fix
'autotok' is not recognized / command not found	Run uv tool update-shell once and open a new terminal. If you installed with pip instead, use python -m autotok ...
Chromium for Playwright is not installed	autotok install-browser (Linux servers: add --with-deps)
TikTok rejected the session / session rejected	autotok login -n NAME --force (check with autotok accounts check NAME)
Invalid parameters (status_code=5)	TikTok changed its upload API. Please open an issue with the full error.
potential violation of our Community Guidelines	TikTok blocked that video's content; it isn't a tool error.
Login page refuses to log in / shows a captcha loop	Try your installed Chrome: add AUTOTOK_BROWSER_CHANNEL=chrome to your .env, or copy the sessionid cookie from your browser and use autotok login -n NAME --sessionid ...
"Verify it's really you" during a cloud login	TikTok doesn't recognise the cloud browser's IP. Complete it in the live view (choose Email), or avoid it with a proxy; see the notes under Cloud browsers
Cloud login live view is blank (self-hosted Steel)	Restart steel-browser with DOMAIN=localhost:3000 (its address)
Browserbase ... (HTTP 402): Proxies are not included in the free plan	Remove BROWSERBASE_PROXY_COUNTRY, or the account's proxy for cloud logins, or upgrade the Browserbase plan
No TikTok datacenter cookie saved warning	Log in again with autotok login, or pass --datacenter with --sessionid
may or may not have been posted	The connection dropped while publishing. Check the account before retrying, to avoid a duplicate.

See also Common problems.

---

Professional Software (autotok Pro)

Fill waiting list form: https://forms.gle/M4KpdfruqCukQvj99

If you are looking for something more, which can get you faster to your goal, I offer software which can:

• Handle more than 1000 accounts
• Upload identical videos to multiple accounts automatically
• Schedule videos for multiple accounts, 20 days to 2 years in advance
• Automatically source videos from YouTube, X, Reddit, TikTok
• Setup uploading pipelines, from source to uploading schedule
• Metrics for viewing current performance of these different accounts
• Personalised support from me for any issues you may face for up to 3 months
• Proxy support, clean and modern UI

Available for purchase, if interested please email me at [email protected] with subject line Tiktok Bot Software or else I might miss the email.

---

Licensing

autotok is dual-licensed:

• Open source: GNU AGPL v3.0. Use, modify and share it freely. If you distribute a modified version, or run one as a service for others, you must publish your source code under the same licence.
• Commercial: to build autotok into closed-source products or paid services without the AGPL obligations, or to use autotok Pro, contact [email protected].

Copyright © 2021–2026 Michael Peres. Releases before 2.0.0 remain under the licence they were published with. The bundled signing scripts are third-party code, see THIRD_PARTY_NOTICES.md. Contributions are welcome under the terms in CONTRIBUTING.md.

---

Support This Project

If you like the work provided, please consider supporting me through Patreon or Ko-Fi, or star the project.

• Thanks @DelvinBa for updating to TikTok's new upload endpoint. (09/12/2024)

Bugs and Issues

Please report bugs in the issues tab rather than by email.

Notes and Terms

This project is not affiliated with TikTok. Automating uploads may break TikTok's terms of service and can get accounts restricted or banned. Only upload content you have the rights to. Use at your own risk.

Star History