Multi-Accounting for Stock Photo Agencies: Contributor Accounts
How stock photo agencies manage dozens of contributor accounts across Shutterstock, Adobe Stock and more without triggering fraud flags or losing payouts.
Why stock photo contributors need multi-accounting at all
A contributor rarely sells through just one marketplace. Royalty rates on Shutterstock, Adobe Stock, iStock, Depositphotos and Dreamstime are calculated differently, payouts land on different schedules, and demand for the same image or clip can vary wildly between platforms. So both independent creators and agencies that manage portfolios of dozens of photographers and videographers end up running a separate account on every platform — sometimes several per region, if a platform splits its storefronts by country.
An agency managing 30–50 contributors typically juggles 150–300 accounts: 4–6 platforms per person. Each contributor has their own ID, their own tax form, their own usual login location. Mixing all of that into one browser means either exposing the link between different people's accounts or losing control over who's uploading what.
What counts as a violation and what's normal practice
It helps to separate two situations clearly.
One person creating multiple personal accounts on the same platform to dodge limits or resell the same content under different profiles — that's a violation of most stock photo sites' terms. Contributor policies almost everywhere prohibit duplicate accounts belonging to one author on one service.
An agency that officially manages accounts belonging to different real people — photographers, videographers, illustrators — with their consent and under contract, isn't breaking anything. That's a standard operating model for creative agencies and production houses: a manager uploads content, handles moderation queries, and manages metadata and keywords on the author's behalf, but the account itself belongs to the author. The difference isn't the number of profiles open in a browser — it's who actually owns those accounts and whether the platform is aware of the arrangement.
In this model, an antidetect browser isn't a way to hide from the rules. It's a tool for keeping dozens of real accounts, owned by different real people, organized and separate.
What goes wrong without separated profiles
Contributors get linked to each other. A browser doesn't just store a login and password — it carries a bundle of parameters: device fingerprint, cookies, history, often an IP address. If an agency manager logs into three different photographers' accounts from one Chrome profile, the platform's fraud detection sees an identical fingerprint and the same IP across different logins. To the platform, that looks like one person running several accounts — exactly what's prohibited. Explaining afterward that it's actually an agency managing distinct real authors, not one person, falls on the contributor, not the manager.
Metadata and keyword mix-ups. When dozens of accounts are open in a jumble, browser history and autofill turn into a mess: suggestions from one account bleed into another, and it's easy to accidentally upload work to the wrong platform or save someone else's payout details by mistake.
Verification headaches. Stock sites ask contributors to confirm identity and tax status — passport, address, sometimes a video call. If the IP used during verification doesn't match the country on the documents, that's grounds for manual review and payout delays measured in weeks.
Lost access when a manager leaves. If all passwords and sessions live in a staff member's personal browser, their resignation or a laptop replacement puts a chunk of the account portfolio at risk.
How a per-contributor profile is structured
The logic is simple: one GetAntik profile equals one contributor on one platform, not one contributor overall. If an author sells on four stock sites, they get four isolated profiles, each with its own set of parameters:
- Browser fingerprint — OS, browser version, screen resolution, core count, canvas/WebGL/audio noise, fonts. The goal isn't to fabricate a fake identity but to give each account a stable, internally consistent technical environment that doesn't jump around between sessions and doesn't match the fingerprint of a neighboring profile.
- A proxy matching the contributor's country. If an author lives in Poland but logs in from a Dutch IP, that mismatch is visible to the platform and sometimes flags the account for review. The proxy manager makes it easier to keep that binding consistent: one proxy, one profile, one country, plus regular checks that the IP is still alive and not blacklisted.
- Cookies and browsing history for that specific account, without mixing with others. If you need to move a contributor's session to another device or back it up before replacing a computer, exporting and importing cookies covers that — the process is detailed in the piece on backing up profile sessions.
- 2FA for that account. Two-factor authentication is mandatory for payouts on many stock sites. Storing codes in a manager's email is a bad habit — if the staff member changes or email access is temporarily lost, you can lose the ability to log into the author's account. A built-in 2FA key vault per profile removes that risk: the code is generated right alongside the account itself.
A fast start for a new platform or a new contributor
When an agency onboards a new photographer, or adds a new platform for an existing one, setting up a profile from scratch every time wastes hours. It's smarter to keep a template ready: baseline fingerprint settings tuned for a specific stock service, a bookmark structure for the sections that matter (upload, stats, payouts), and the list of extensions actually needed for metadata work. This approach to templates is covered in the article on templates for fast account setup — for an agency onboarding 5–10 new accounts a month, it saves real hours of manual configuration.
The agency team: who sees what
- lev opened Airdrop zkSync 07
- artem closed FB · US · BM-14
- maya is watching artem
- lev transferred TikTok Shop 03
An agency typically has several roles: a content manager who uploads and tags material, a payouts specialist who tracks tax forms and payment details, and a lead who sees everything. Team access to profiles lets you assign each person their own slice of the pool — Manager A sees only their ten contributors, Manager B sees theirs. A separate finance role gets access to accounts where payouts need checking, without necessarily being able to edit uploads.
This cuts the risk of accidental mistakes: someone whose job is purely tagging simply can't open an account holding someone else's payment details if they don't have permission to.
Proxies: a separate issue for stock sites
For stock photo platforms, a proxy doesn't just solve anonymity — it solves credibility. The platform wants to see a contributor logging in from roughly the country stated on their tax documents, and an IP that doesn't jump between continents every day. That doesn't mean the IP can never change — trips, moves, and switching providers happen to real people. But sharp, frequent, unexplained geolocation swings are a common trigger for manual account review by platform support.
There's also a meaningful difference between residential and datacenter proxies. For logging into a personal account, where looking like an "ordinary user" matters, residential IPs are usually more reliable — they belong to real ISPs in a specific region. The logic of choosing a proxy type for a given task, and when to actually rotate an IP versus leave it alone, is covered in the article on IP rotation strategy for profiles.
Budget: what this costs at scale
An agency with 40 contributors averaging 4 platforms each needs 160 profiles. The Team plan (300 profiles, $79/month) covers that comfortably with room to grow, plus spare profiles for test uploads and backup accounts. If you're managing fewer than 20 contributors, the Base plan at 100 profiles for $44 is enough.
On top of that comes proxy cost — usually a separate line item billed by the number of active IPs rather than the number of browser profiles. For an agency where some contributors log in rarely, it's smarter not to keep a proxy permanently paid for every single profile and instead handle it selectively. How to budget a team's profiles and proxies together is worked through in the piece on multi-accounting unit economics.
Common agency mistakes
One browser profile shared across several contributors "to save money." The savings turn into the risk of a mass suspension: if a platform's fraud detection links several accounts by fingerprint, all of them get flagged for review at once, not just one.
Using "whatever proxy is available" without matching the author's country. A cheap shared proxy from a random location is a frequent cause of payouts stuck in verification.
Storing passwords and 2FA in a manager's personal notes. If that staff member leaves or loses their phone, the agency risks going days or weeks without access to part of its portfolio.
Ignoring the difference between "agency" multi-accounting and fake multi-accounting. If a contributor exists only on paper and all the content is actually uploaded by one person under different identities, that's not role separation — it's exactly what platforms prohibit. An antidetect browser doesn't fix that, and shouldn't be used to run that kind of scheme.
No shared log of who uploaded what. When a copyright dispute or metadata question comes in six months after an upload, it helps to know exactly which manager handled that specific file and when.
Protecting agency data
Stock photo accounts are tied to contributors' personal data and payout details, so securing profile data matters just as much as it does for financial services. Profile data is encrypted on the device using the account password, and the server has no access to its contents — this closes off the scenario where a breach at the antidetect browser provider automatically means a leak of contributors' account passwords. More on the encryption and recovery mechanics is on the security page.
FAQ
Can a contributor use an antidetect browser to manage several of their own personal accounts on the same stock site? If a platform explicitly bans multiple personal accounts belonging to one author on the same service, an antidetect browser doesn't change that — it only separates sessions technically. You still need to follow that platform's specific policy.
Does each platform need its own proxy, or can one proxy cover a contributor across all their accounts? It's better to tie a proxy to the contributor's geography rather than to a specific platform — that way all of their accounts look consistent with one real location, even across four different platforms.
What happens when a contributor is handed off from one agency manager to another? The profile, with all its settings, cookies, and saved 2FA keys, transfers within the team pool without changing the account password and without a fresh login — removing the risk of an accidental suspension during the handoff.
Should an agency install metadata autofill extensions across every profile at once? It's safer to add an extension only to the profiles that actually need it rather than globally — that way a stray extension doesn't affect the fingerprint of accounts where it isn't required.
If you're managing a portfolio of photographers or videographers across multiple stock sites, start with the free plan for 3 profiles, set up a couple of contributors, and see how isolated profiles hold up during verification and moderation before migrating the whole pool.