Bulk-creating 100 profiles with random fingerprints in Incogniton

Managing multiple accounts at scale means spending a lot of time on setup if you do it manually. Creating profiles one by one in any antidetect browser is fine for five profiles, maybe ten, but once you’re running 50 to 100 accounts across platforms like Facebook Ads, Amazon, or airdrop campaigns, the setup overhead becomes a real bottleneck. One typo in a fingerprint field, one proxy you forgot to assign, and you’ve got a contaminated profile sitting in a pool you thought was clean.

Incogniton has a bulk profile creation feature that solves most of this. Instead of clicking through a creation wizard 100 times, you configure a template once, set the randomization rules, feed in a proxy list, and let the tool generate the profiles. i’ve used this workflow for campaign setups where i needed a clean slate of 80-100 profiles on a deadline, and it’s saved a couple of hours per batch compared to doing it by hand in other tools.

This guide covers the full process from prerequisites through to verifying the profiles are actually fingerprint-distinct. it’s aimed at operators who already know why they need antidetect profiles and just need to execute the bulk setup efficiently. by the end you’ll have 100 profiles with randomized canvas, WebGL, fonts, screen resolution, timezone, and user agent, each assigned a unique proxy.

what you need

Incogniton account on a paid plan. The free Entrepreneur plan caps you at 10 profiles. You need at minimum the Starter plan ($29.99/month, 50 profiles) or the Professional plan ($79.99/month, 150 profiles) to hold 100 profiles. Check current pricing on the Incogniton website before you buy.
100 unique proxies. one profile, one proxy, no sharing. residential or mobile proxies are preferable depending on the platform you’re targeting. datacenter proxies work for lower-risk platforms. proxies should ideally match the geo you’re spoofing in the fingerprint timezone.
A proxy list in CSV or plain-text format, one proxy per line, in the format host:port:username:password or socks5://user:pass@host:port.
Basic familiarity with browser fingerprinting concepts. if you’re new to this, the EFF’s Cover Your Tracks tool is a good primer on what gets measured and why it matters.
Windows or macOS machine. Incogniton is a desktop application. Linux is not officially supported.
Around 30-45 minutes for initial setup, plus time to run fingerprint checks afterward.

step by step

step 1: install and log in to Incogniton

Download the latest desktop installer from the Incogniton downloads page. Install it and log in with your account credentials. if you’re on a team, make sure your seat has profile creation permissions enabled by your workspace owner, otherwise the bulk create button will be greyed out.

expected output: you land on the profile overview dashboard. the sidebar shows your profile count (should be 0 or whatever you already have).

if it breaks: if the app fails to launch after install, check that your Windows version is at least Windows 10 21H2 or macOS 12+. Incogniton’s Chromium core has dropped support for older OS builds since their 5.x releases.

step 2: prepare your proxy file

Format your proxy list as a plain text file with one proxy per line. Incogniton’s bulk import expects this format:

socks5://username:password@hostname:port
http://username:password@hostname:port

Or the colon-separated format:

hostname:port:username:password

Save this as proxies.txt. keep the file somewhere easy to locate, you’ll be importing it from the file picker in a later step.

expected output: a clean .txt file, 100 lines, no blank lines, no headers.

if it breaks: if you’re getting proxies from a provider dashboard, some export formats include extra columns (country, ASN, etc.). strip those out. Incogniton’s importer is strict about format and will silently skip lines it can’t parse.

step 3: open the bulk profile creation dialog

From the Incogniton dashboard, click the “New Profile” dropdown button (the small arrow next to the main create button) and select “Bulk Create Profiles”. this opens the bulk creation modal. some older UI versions label this as “Mass Create”, same feature.

expected output: a modal dialog appears with fields for profile count, naming convention, OS, browser version, and fingerprint options.

if it breaks: if the dropdown option is missing, you may be on the free plan or a plan that doesn’t support bulk creation. log out and log back in to force a plan refresh if you’ve recently upgraded.

step 4: configure the profile template

In the bulk create dialog, fill out the template fields:

Number of profiles: set to 100.
Profile name prefix: use something descriptive, e.g. fb-us-may26-. Incogniton will append an auto-incrementing number, giving you fb-us-may26-001 through fb-us-may26-100.
Operating System: match your target platform’s dominant user base. for Facebook Ads or Google, Windows 10/11 is safest. for TikTok mobile, you’d normally use Android profiles, though Incogniton’s mobile fingerprint support is limited, Android emulation is available under the OS dropdown.
Browser version: pick a Chromium version in the middle of the current range, not the absolute latest. platforms that see a lot of traffic from Chrome 124 users are more suspicious of someone running Chrome 135 on day one of a release.
Group: assign to a new group (create one called batch-may26 or similar). this makes it much easier to run actions on all 100 profiles together later.

expected output: template fields are filled, profile count shows 100.

if it breaks: if the OS dropdown is showing fewer options than you expect, your Incogniton version may be out of date. check for updates via the in-app updater or re-download from the site.

step 5: configure fingerprint randomization

This is the critical step. Incogniton’s bulk creator has a randomize section with toggles for individual fingerprint components. enable all of the following:

Canvas fingerprint: randomize. this is the most commonly checked signal.
WebGL vendor and renderer: randomize. BrowserLeaks has a good explanation of how this gets read.
Screen resolution: randomize from a set of common values (1920x1080, 1366x768, 1440x900, 2560x1440). Incogniton samples from a built-in distribution, you’re not picking each one manually.
Fonts: randomize. font enumeration is one of the older fingerprinting vectors and still widely used.
Timezone: if all 100 profiles are targeting a single geo (e.g. US-based accounts), set timezone to America/New_York or America/Los_Angeles explicitly rather than randomizing. randomizing timezone across continents while targeting a single market looks suspicious.
Language: set explicitly to match your target geo, e.g. en-US.
User Agent: enable auto-match to OS. this makes sure your user agent string doesn’t contradict the OS and browser version you set above.

Do not enable every randomization toggle blindly. timezone and language should be intentional, not random, if you’re targeting a specific region.

expected output: randomization settings saved in the template.

if it breaks: if you save and the profiles show the same canvas hash across all of them, you’re likely on a version with a known randomization bug. Incogniton has had a couple of these in minor releases. update to the latest version and re-run the batch.

step 6: import proxies

In the same bulk create dialog, find the proxy assignment section. select “Import from file” and point it at your proxies.txt. Incogniton will attempt to match one proxy per profile sequentially. if you have exactly 100 proxies and 100 profiles, each gets one.

After import, run the “Check Proxies” function inside the dialog. this makes a test connection through each proxy and flags any that are dead or unreachable.

expected output: proxy check shows 100 green checkmarks. any red ones need to be replaced in your proxy file before proceeding.

if it breaks: if the proxy check times out for all proxies simultaneously, it’s usually a local firewall or antivirus blocking Incogniton’s outbound connections. add an exception for the Incogniton executable. if individual proxies fail, contact your proxy provider with the specific IPs.

step 7: create the profiles

Click “Create”. Incogniton will generate all 100 profiles in sequence. on a mid-range machine this takes 30-90 seconds depending on the number of profiles and your storage speed (profiles are written to disk during creation).

expected output: 100 profiles appear in your dashboard under the batch-may26 group.

if it breaks: if creation stops partway through and some profiles are missing, check your plan’s profile limit. if you were at 20 profiles before this batch, you need headroom for 100 more. delete old profiles or upgrade your plan.

step 8: verify fingerprint uniqueness

Open 5-10 profiles at random and navigate each to BrowserLeaks or coveryourtracks.eff.org. compare the canvas hash, WebGL renderer, and screen resolution across the sampled profiles. they should all differ.

If two profiles share an identical canvas hash, the randomization did not apply correctly. delete the batch, update Incogniton, and re-run from step 3.

expected output: distinct fingerprint values across all sampled profiles. no two profiles sharing the same canvas hash.

common pitfalls

1. Randomizing timezone across geographies. If you’re building accounts for a US platform and some profiles come up with Asia/Tokyo timezones, that’s a red flag in behavioral analysis. lock timezone to the target region.

2. Reusing proxies across profiles. even if profiles have distinct fingerprints, sharing an IP collapses them into the same identity cluster from the platform’s perspective. one proxy per profile, no exceptions.

3. Not checking proxy quality before creating profiles. it’s easier to swap out dead proxies before the profiles exist than to re-edit 20 profiles after the fact. always run the proxy check in step 6.

4. Ignoring user agent and OS consistency. a profile set to Windows 11 with a Chrome 90 user agent is a mismatch. older Chrome versions don’t run on Windows 11 by release timeline. Incogniton’s auto-match handles this if you leave it enabled, but manually overriding user agent without checking compatibility is a common mistake.

5. Bulk creating without a naming convention. 100 profiles named Profile 1 through Profile 100 are impossible to manage when you’re trying to find the set assigned to a specific campaign or proxy pool. establish a naming prefix before you create.

scaling this

At 10x (1000 profiles): the manual proxy import and verification step becomes the bottleneck. at this scale you want scripted proxy assignment via Incogniton’s REST API rather than file import. the API is available on Professional and higher plans. if you’re doing airdrop farming at this scale, the multiaccountops.com blog has relevant workflow notes.

At 100x (10,000 profiles): Incogniton’s desktop app is not the right tool for this volume. you’re looking at headless antidetect solutions, custom Chromium builds with fingerprint injection, or enterprise-tier tools. the per-seat cost on desktop antidetect products also becomes prohibitive.

Infrastructure changes at scale: at 1000+ profiles you need a proxy management layer, not just a flat list. residential proxies with rotation APIs, sticky session handling, and geo-targeting become essential. managing this manually via text files breaks down fast.

where to go next

Browse the full antidetectreview.org article index for more operator-focused guides.

Written by Xavier Fok

disclosure: this article may contain affiliate links. if you buy through them we may earn a commission at no extra cost to you. verdicts are independent of payouts. last reviewed by Xavier Fok on 2026-05-22.