TikTok Username Checker — Available or Taken
Pricing
from $4.00 / 1,000 results
TikTok Username Checker — Available or Taken
Bulk-check if TikTok usernames are available or already taken. Lightweight HTTP. Pay only for successful checks.
Pricing
from $4.00 / 1,000 results
Rating
0.0
(0)
Developer
Clovys
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
4 days ago
Last modified
Categories
Share
What does TikTok Username Checker do?
TikTok Username Checker tells you whether a TikTok handle is available or already taken. Paste a list of usernames (or profile URLs), run the Actor, and download clean JSON / CSV / Excel from the dataset.
Built for bulk brand / handle research (up to 100,000 usernames per run). Large lists are auto-split into ~3,000-item child runs on Apify, with auto-heal under rate limits. Lightweight HTTP - no browser, 256 MB default.
This Actor is not affiliated with TikTok / ByteDance. Availability is inferred from public profile pages and can change if TikTok alters their HTML.
Key features
- Bulk checks - up to 100,000 usernames per run (invalid / duplicate inputs filtered before work starts)
- Auto-sharding - runs above ~3,000 usernames split into child runs; one parent dataset
- Auto-heal - on blocks / timeouts: backoff and lower concurrency without burning extra proxy
- Available vs taken - boolean
availableplus display name when taken - URL-aware input -
@user,user, orhttps://tiktok.com/@user - No browser - fast HTTP crawler-style requests (low compute)
- Success-only billing - only conclusive checks (
availabletrue/false) charge PPEresult - Export anywhere - JSON, CSV, Excel, HTML from the Apify dataset
Why Clovys
Clovys is a nonprofit organization driven by a single mission: to make the internet safer, faster, more reliable, and universally accessible.
We believe that data should not be locked behind exorbitant paywalls or complex technical barriers. By building lightweight, highly optimized Apify Actors, we help developers, researchers, and organizations access the information they need to innovate without friction.
As a nonprofit initiative, we do not optimize for margins. Our pricing is kept as low as possible and is strictly calculated to cover the raw infrastructure costs of data extraction - such as Apify compute units and proxy bandwidth.
For TikTok specifically, Clovys focuses on a cheap, parallel HTTP path so large handle lists stay affordable at Store scale.
Use cases
- Brand protection - see if your brand handle is free on TikTok
- Launch naming - screen shortlists of product / campaign usernames
- Agency workflows - bulk-check client name ideas before pitching
- Multi-platform suites - pair with other Clovys username checkers
How to use
- Open TikTok Username Checker in Apify Console
- Paste usernames in Usernames (prefill is a single handle for cheap Store health checks)
- Keep defaults (256 MB, concurrency 3)
- Click Start
- Download results from the Dataset tab (JSON, CSV, Excel, ...)
Input
| Field | Type | Default | Description |
|---|---|---|---|
usernames | string[] | - | Usernames or profile URLs (required, up to 100,000) |
maxConcurrency | integer | 3 | Parallel checks (1-10) |
maxRetries | integer | 2 | Retries on network / ambiguous responses |
requestDelayMs | integer | 200 | Pause after each check (0 = off) |
Output example
You can download the dataset in JSON, HTML, CSV, or Excel.
{"platform": "tiktok","username": "khaby.lame","available": false,"displayName": "Khabane lame","profileUrl": "https://www.tiktok.com/@khaby.lame","title": "Khabane lame on TikTok","method": "public_profile_crawler_ua","checkedAt": "2026-09-26T01:00:00.000Z","error": null}
Taken and available rows are successful results. Ambiguous / failed rows keep available: null and error set - they are not billed.
Data fields
| Field | Description |
|---|---|
platform | Always tiktok |
username | Normalized handle |
available | true = free, false = taken, null = inconclusive |
displayName | Public name when taken |
profileUrl | Canonical profile URL |
title | Page <title> when captured |
method | Check method used |
checkedAt | ISO timestamp |
error | Error message if the check failed |
Pricing
Pay-per-event pricing (platform usage is billed separately by Apify):
| Event | When charged | Price |
|---|---|---|
| result | Each conclusive check (available true or false) | $0.004 ($4 / 1,000) |
| Actor Start | Once when the run starts (scaled by memory GB) | $0.001 |
Example: 1,000 conclusive checks ~ $4.00 in PPE result (+ Actor Start + Apify platform usage).
Only conclusive results are charged as result. Failed / ambiguous rows are free on the PPE event.
Recommended settings
| Goal | Settings |
|---|---|
| Production / Store | 256 MB, concurrency 3, delay 200 ms |
| High volume | concurrency 5-8, delay 50-100 ms |
| Huge lists | up to 100,000 usernames - auto-shard handles the rest |
FAQ
How many usernames per run? Up to 100,000. Lists above ~3,000 are auto-split into child runs; invalid / duplicate inputs are dropped before sharding.
Is "taken" billed? Yes. Both available: false (taken) and available: true (free) are conclusive result events. Only error / inconclusive rows are free.
Do I need expensive proxies? Usually no for moderate volumes. If you hit rate limits, lower concurrency, raise delay, or add Apify proxy.
What if a check fails? It is stored with error and available: null. Other usernames continue. Failed items are not billed as result.
Is this official TikTok data? No. This Actor is independent and unaffiliated. TikTok can change page behavior at any time.
Support
Questions, bugs, or feature requests: use the Actor Issues tab on Apify, or contact Clovys through the Store profile.