AutoSocial is a free, open source marketing & customer engagement project written in JavaScript and released under MIT. It has 1,503 GitHub stars, 305 forks and 4 open issues, and was last pushed 5 months ago. On this registry it ranks #62 of 78 tracked projects in Marketing & Customer Engagement, with 5 head-to-head comparisons available.

What is AutoSocial?

AutoSocial Studio is a local, MIT-licensed JavaScript dashboard that runs short-form video posting workflows for TikTok, Instagram, and YouTube from a single workstation, built for indie builders and small teams who would rather keep their account sessions on their own machine than hand them to a hosted service.

What it is

AutoSocial Studio is a Node.js application that combines a local Express dashboard, Playwright-powered upload flows, per-account queues and schedulers, yt-dlp downloader utilities, and an FFmpeg-based video uniquifier. It lives in the JavaScript and Node.js ecosystem, requiring Node.js 18 or newer, and is explicitly built for a local workstation: the project states that it is not a hosted SaaS app and that it ships without user authentication. Accounts, queues, and browser sessions are organized from one local control plane covering TikTok, Instagram, and YouTube.

The problem it solves is distribution rather than production. The README observes that AI coding tools have made it easier for indie builders to ship products, while distribution remains the hard part. AutoSocial Studio turns launch clips, demos, product updates, and short-form experiments into a repeatable local marketing workflow without handing account sessions to a hosted service. The project is explicit that the goal is a practical creator operations dashboard — organizing accounts, preparing queues, scheduling posts, reusing captions, downloading reference material, and processing videos — and not mass posting or engagement spam.

Key capabilities

  • Manages multiple brands and accounts with isolated queues and browser sessions, persisting Playwright login sessions under .profiles/.
  • Posts queued videos to TikTok, Instagram, and YouTube, with a First-Run Setup page that verifies local dependencies, login sessions, and queue folders.
  • Schedules posts using cron expressions, daily times, or an instant-post mode, configured per platform through CRON_EXPRESSION, INSTAGRAM_CRON_EXPRESSION, and YOUTUBE_CRON_EXPRESSION.
  • Downloads recent TikTok videos with yt-dlp and fans them out into queues, and scans or downloads TikTok profiles into autodownload/profile_downloads.
  • Runs FFmpeg-based video uniquification from the dashboard or the CLI, with an optional user-provided logo overlay set by UNIQUIFY_LOGO_IMAGE.
  • Exposes workflow tuning through environment settings such as POST_DELAY_MS, POST_PUBLISH_HOLD_MS, FAILURE_HOLD_MS, RANDOM_QUEUE_ORDER, and DEFAULT_CAPTION.
  • Binds the dashboard to 127.0.0.1 by default, applies a same-origin guard to mutating requests, and blocks binding to a non-local address unless explicitly permitted.

Who uses it and how

  • Indie hackers launching multiple products, who need separate brand queues and browser sessions for each one.
  • AI builders who ship with AI coding tools and want a repeatable content workflow for launch clips and demos afterwards.
  • Small teams that prefer local browser sessions over a hosted service storing their account credentials.
  • Maintainers and contributors experimenting with responsible automation around product updates, demos, and community content.
  • Windows users running the bundled yt-dlp.exe workflow from autodownload/, which the README names as the primary target for downloader features.

Getting started

Run npm ci, then npx playwright install chromium and npm run doctor; copy .env.example to .env and start the dashboard with npm run dashboard, which serves at http://127.0.0.1:3000. Begin in the Setup view, which checks local dependencies and shows the exact pending folders where videos should be dropped for each platform.

How it compares

The facts provided do not name any paid products or similar tools, so AutoSocial Studio stands alone in this registry. Its distinguishing position, as the README frames it, is architectural rather than competitive: automation runs on the operator's own workstation and keeps credentials in local Playwright sessions instead of a hosted service.

When to use it — and when not to

A self-hoster must operate Node.js 18+, npm, Playwright Chromium, and FFmpeg with ffprobe on the PATH, plus an optional yt-dlp.exe for downloader features, so it suits someone comfortable maintaining a local toolchain. It should not be chosen by anyone wanting a multi-user or remotely hosted service, because the dashboard has no authentication layer and is meant to stay local. Note also that the sample configuration ships without a default caption, watch channel, logo, or sound query, and that the bundled downloader workflow targets Windows primarily.

project readme (upstream, from github) — read inline

AutoSocial Studio

CI License: MIT Node.js >=18

AutoSocial Studio is a local, multi-account automation dashboard for short-form video workflows across TikTok, Instagram, and YouTube. It combines a local Express dashboard, Playwright-powered upload flows, per-account queues, schedulers, yt-dlp downloader utilities, and an FFmpeg-based video uniquifier.

This project is built for a local workstation. It is not a hosted SaaS app and does not include user authentication.

AutoSocial Studio dashboard

Why This Exists

AI coding tools make it easier than ever for indie builders to ship products. Distribution is still the hard part. AutoSocial Studio helps builders turn launch clips, demos, product updates, and short-form experiments into a repeatable local marketing workflow without handing account sessions to a hosted service.

The goal is not mass posting or engagement spam. The goal is a practical creator operations dashboard: organize accounts, prepare queues, schedule posts, reuse captions, download reference material, and process videos from one local control plane.

Who It Helps

  • Indie hackers launching multiple products.
  • AI builders who need a repeatable content workflow after shipping with AI coding tools.
  • Small teams that want local browser sessions instead of a hosted service storing account credentials.
  • Maintainers and contributors experimenting with responsible automation around product updates, demos, and community content.

Features

  • Manage multiple brands/accounts with isolated queues and browser sessions.
  • Use the First-Run Setup page to verify local dependencies, login sessions, and queue folders.
  • Post queued videos to TikTok, Instagram, and YouTube.
  • Persist Playwright login sessions under .profiles//.
  • Schedule posts with cron expressions, daily times, or instant-post mode.
  • Download recent TikTok videos with yt-dlp and fan them out into queues.
  • Scan/download TikTok profiles into autodownload/profile_downloads.
  • Run FFmpeg-based video uniquification from the dashboard or CLI, with an optional user-provided logo overlay.

Requirements

  • Node.js 18+
  • npm
  • Playwright Chromium
  • FFmpeg and ffprobe in PATH
  • Optional: yt-dlp.exe in autodownload/ for downloader features

Windows is the primary target for the bundled yt-dlp.exe workflow, but the dashboard and core Node services are ordinary Node.js.

Quick Start

npm ci
npx playwright install chromium
npm run doctor

Create your local environment file:

Copy-Item .env.example .env

Start the dashboard:

npm run dashboard

Open http://127.0.0.1:3000.

Start with the Setup view. It checks local dependencies and shows the exact pending folders where videos should be dropped for each platform.

Configuration

Copy .env.example to .env and review the values that matter for your workflow.

Common settings:

  • CRON_EXPRESSION, INSTAGRAM_CRON_EXPRESSION, YOUTUBE_CRON_EXPRESSION
  • TZ, BROWSER_LOCALE
  • HEADLESS
  • POST_DELAY_MS, POST_PUBLISH_HOLD_MS, FAILURE_HOLD_MS
  • AUTO_ADD_SOUND, DEFAULT_SOUND_QUERY
  • RANDOM_QUEUE_ORDER
  • DEFAULT_CAPTION
  • UNIQUIFY_LOGO_IMAGE
  • WATCH_CHANNEL, WATCH_INTERVAL, WATCH_MAX_VIDEOS, WATCH_MIN_VIEWS
  • AUTO_POST_PLATFORMS
  • DASHBOARD_HOST, DASHBOARD_PORT

Hashtag captions in .env should be quoted:

DEFAULT_CAPTION="#mybrand #shorts"

The sample config ships without a default caption, watch channel, logo, or sound query. Set those in .env or in the dashboard for your own workflow.

Dashboard Security

The dashboard binds to 127.0.0.1 by default and has no authentication layer. Keep it local.

Mutating dashboard requests include a same-origin guard so random websites cannot blindly trigger local dashboard actions through the browser.

Binding to a non-local address is blocked unless DASHBOARD_ALLOW_REMOTE=true is set. Only use that on a trusted network and only if you understand that anyone who can reach the dashboard can operate the local automation controls.

See SECURITY.md for more details.

First-Time Login

Open the dashboard, go to Accounts, and start a login session for each platform you want to use. Sessions are stored on disk and reused between runs.

The CLI login command is still TikTok-specific:

npm run login

Queue Layout

Queues are account-aware:

queue/<account>/tiktok/pending
queue/<account>/instagram/pending
queue/<account>/youtube/pending

Successful uploads move into posted; failed uploads move into failed.

Supported video extensions:

  • .mp4
  • .mov
  • .webm
  • .avi
  • .mkv

Caption sidecars can use the same base filename:

  • .description
  • .txt

Commands

npm run dashboard
npm run clean:debug
npm run doctor
npm run check
npm run login
npm run post
npm run daemon
npm run uniquify
npm run video-info -- --video "C:\path\video.mp4"
npm run autodownload

Notes:

  • The dashboard is the preferred workflow.
  • clean:debug removes local debug screenshots and dashboard logs only.
  • login, post, and daemon are TikTok CLI flows.
  • Instagram and YouTube posting are managed through the dashboard.
  • uniquify and video-info require FFmpeg and ffprobe.
  • autodownload requires yt-dlp.

Development

Run the local checks:

npm run check
npm audit --omit=dev

The test suite focuses on local logic that does not require live social platform access: queue handling, sidecars, filesystem archiving, scheduler time logic, and config parsing.

Runtime Data

Do not commit local runtime data. The .gitignore covers known generated paths, including:

  • .env
  • .profiles/
  • .scheduler-state/
  • *-state.json
  • queue/
  • downloads/
  • user-assets/
  • autodownload/downloads/
  • autodownload/profile_downloads/
  • autodownload/info.json
  • last-*.png

Before publishing a fork, inspect git status --short and git status --ignored.

Responsible Use

Users are responsible for complying with platform terms, account policies, rate limits, local law, and content rights. This project does not grant permission to post content you do not own or have permission to use.

Prefer official platform APIs where they are available for your workflow. Avoid spam, deceptive behavior, unauthorized scraping, and posting without consent. Keep sessions local, rotate credentials if they are exposed, and review platform limits before enabling scheduled automation.

Roadmap

See ROADMAP.md for planned work around safer automation controls, official API integrations, creator workflow templates, and maintainer tooling.

License

MIT. See LICENSE.

Frequently asked questions

Is AutoSocial free to use?

AutoSocial is open source under the MIT licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does AutoSocial do?

Local social media automation dashboard for TikTok, Instagram, and YouTube.

What is AutoSocial written in?

AutoSocial is primarily written in JavaScript. Its source is publicly available at https://github.com/Katzca/AutoSocial, and it has 1,503 GitHub stars.