Site Sync

Multi-Site Sync Overview

Learn about AniBT multi-site automatic synchronization: publish once to dispatch across Bangumi Moe, Mikan, DMHY, ACGNX, ACG.rip, and Nyaa.

AniBT supports seamless "publish once, synchronize everywhere" capabilities. Fansub groups only need to submit a release once on AniBT, and our background system automatically synchronizes the torrent file, title, category, and release notes to major external BT distribution sites.

Site sync is exclusively available to fansub groups. Complete Fansub Onboarding before configuring. Credentials are encrypted and configured per site in your console at /groups/<slug>/sync.

Sync Workflow & Status Tracking

Once a release is accepted on AniBT, asynchronous tasks are queued for each enabled external destination:

Save and Test Credentials

Visit /groups/<slug>/sync in your fansub console and enter credentials for your chosen sites. Always click "Test Connection" to ensure valid credentials before publishing. When the test finishes, the page tells you whether it passed or failed, with the reason for a failure.

Automated Dispatch on Release

When submitting anime or other releases, AniBT automatically schedules uploads to all enabled external sites. Each upload is processed independently in background queues; temporary connection dips on one site do not affect others.

For a release published with only a magnet link and no torrent file, AniBT fetches the torrent through the magnet link before sending it to external sites. The torrent sent to external sites is the same one viewers download from AniBT: it keeps only the file information of the torrent, its trackers are the AniBT tracker plus AniBT's default tracker list, and it carries no trackers, web seeds or comment added by third-party torrent caches. The infohash does not change.

Inspect Status & Retry

Click the "Site Sync" status badge on any release card in your console to view real-time sync progress, external URLs, and error diagnostics. When a site fails, a group owner or group admin can click "Retry sync" to resubmit that failed attempt. A retry is refused while the site already has a queued or running job, so repeated clicks do not submit twice.

An attempt whose outcome is uncertain (ambiguous) may already be on the external site, so it offers no retry and still shows as failed. Check the external site first. To submit again, a group owner, group admin or site administrator uses "Resend". Resending submits the release again and may create a duplicate post.

Sync logs refresh about every 5 seconds while tasks are queued or running, and check about every 30 seconds while idle. Tasks started from another page or device may appear at the next check; this does not delay their execution.

While a group's status is Inactive or Suspended, no external publishing task that starts running from then on is sent to an external site, including tasks queued before the status changed. The console cannot publish or edit releases, upload images, import anime, change the group's profile or settings, save external site credentials, test connections, retry or resend sync, create claims, manage title templates, create API keys, invite members or change member roles, and the group's API keys cannot do anything. Only clean-up remains: deleting releases and image host images, revoking API keys, removing members and leaving the group, each with the same permissions as before.

Supported Distribution Platforms

Standard Sync States

When inspecting progress in the console or via the Sync Status API, each platform returns one of the following states:

Prop

Type

Anime claims (binding a seasonal anime to your group and custom title templates) are managed in /groups/<slug>/claims, separate from site sync credentials.

On this page