Two-factor authentication on stock contributor accounts is less uniform than it looks. Adobe documents user-enabled two-step verification and a separately generated SFTP password. Shutterstock documents a risk-triggered one-time passcode and FTPS that uses your ordinary account password. Alamy states its FTP password is the same as your login. Getty, iStock and Depositphotos publish nothing about 2FA outside their signed-in areas.
The advice you will see everywhere, and why it is wrong
The standard reassurance runs like this: FTP uses its own separate credentials, so turning on two-factor authentication cannot break your upload automation. It is a comforting rule and it is not true across the board. It describes Adobe accurately. It contradicts what Shutterstock and Alamy publish on their own help pages, both of which tell you to put your ordinary account password into your FTP client.
That distinction has a practical edge. Where FTP uses a dedicated, separately generated secret, rotating your account password or adding a second factor leaves your nightly batch untouched. Where FTP uses the account password itself, your login credential and your automation credential are the same string, which means any change to one is a change to the other — and it means a second factor, if an agency ever adds one, lands directly on the path your uploads travel.
2FA and FTP credentials, agency by agency
Compares five stock agencies on what they publish about two-factor authentication for contributors, which credentials their FTP or SFTP upload path uses, and whether they address the interaction between the two. Every cell reflects the agency's own public help pages; unknown means the agency does not publish it outside its signed-in contributor area.
Agency by agency, from their own help pages
Adobe Stock — real 2FA, and a generated SFTP password
Adobe is the clearest case. Its two-step verification setup page describes a user-enabled feature using the Adobe Account Access app, email or SMS, with more than one method allowed at a time, and a separate page covers switching it off while recommending you keep it on. Third-party authenticator apps are not mentioned. On the upload side, Adobe's contributor help walks you through entering your hostname and ID in an SFTP client and then selecting Generate password, noting that all other credentials remain unchanged. Adobe itself says nothing about the two interacting, but because the SFTP secret is generated rather than reused, enabling a second factor on your Adobe sign-in does not touch the string your client holds. That is an inference from the mechanism, not a statement Adobe publishes — worth knowing if you are planning the Adobe Stock upload workflow around it.
Shutterstock — a passcode you cannot turn on, and FTPS on your account password
Shutterstock documents something adjacent to 2FA but not the same thing: its security systems generate a one-time passcode when a suspicious login attempt is detected, described as an additional layer of security. That is risk-triggered, not user-enabled, and the article does not call it two-factor authentication. No Shutterstock page documents a 2FA setting a contributor can switch on. Meanwhile its FTPS instructions are explicit: host ftps.shutterstock.com on port 21, username your contributor email or username, password your contributor account password. Your upload credential and your login credential are one and the same, which is the detail to keep in mind when you set up Shutterstock FTP uploading.
Alamy — the FTP password is the login password, stated outright
Alamy leaves no ambiguity. Its contributor uploading help gives the host as upload.alamy.com, the username as your Alamy email, and states that your password is the same as your Alamy login. Neither that page nor the account help page mentions two-factor or two-step verification anywhere; the only security flow described is an email password reset. The implication is worth stating plainly: because Alamy's own documentation couples the two credentials, a future 2FA rollout at Alamy is exactly the kind of change that would land on contributors' upload automation. Plan the Alamy upload workflow with that coupling in view.
Getty Images, iStock and Depositphotos — nothing published
For these three the honest answer is that there is no public answer. The Getty Images contributor help centre is a signed-in application, so its account-security and FTP articles are unreadable from outside; the public iStock account FAQ covers password rules and email reset with no mention of two-step verification. Depositphotos' public help category for site tools and account settings lists password and email-change articles and no 2FA article, and its contributor FTP FAQ pages are not publicly retrievable. A missing article is not proof a feature is missing, so the correct reading is unknown rather than absent — check inside your own account settings and treat anything you read elsewhere as unverified.
What this means if you upload on a schedule
Automation does not survive an interactive prompt. An FTP client, a cron job or a delivery pipeline connects with a stored secret and either succeeds or fails; there is nobody present to read a code off a phone. So the question for any scheduled upload is not whether an agency supports 2FA, but whether the credential your pipeline holds is the one a second factor would guard. Where the two are separate, as at Adobe, you can harden the account freely. Where they are the same string, as at Shutterstock and Alamy, hardening the login means touching the pipeline. The difference between FTP and SFTP delivery is a separate axis and does not change this one.
One thing to be careful about: app-specific passwords are frequently recommended as the way out of this, and not one of these five agencies documents offering them. Adobe's generate-a-password-for-SFTP flow is the closest real mechanism and it is functionally similar, but Adobe does not call it an app-specific password and nothing equivalent is published by Shutterstock, Alamy, Getty, iStock or Depositphotos. If someone tells you to create an app password for your stock agency, ask them where the agency documents it.
There is also a verification step that is genuinely not 2FA and gets confused with it. Adobe describes phone verification as a one-time security step for new contributors, alongside email verification, and both are required to get started. That is identity checking at onboarding, not a second factor on every sign-in, and switching two-step verification on or off has nothing to do with it.
2FA does not solve the third-party tool problem
Two-factor authentication protects the sign-in. It does nothing about a credential you have already handed to a tool. If a workflow service holds your Shutterstock account password because that is what its FTPS connection requires, that password is now in that vendor's storage, and a second factor on the web login does not reach into it. This is why credential handling is a separate question from account security, and why how you grant a tool access to your stock accounts deserves its own decision rather than being treated as covered by 2FA.
Tool vendors differ sharply here, and some say so. Microstockr's FAQ states that credentials are not stored on its servers and are encrypted on the device, with only subscription status checked server-side. StockSubmitter's page says passwords are stored on your computer only, while the privacy policy of the Microstock+ platform it belongs to describes storing the data used to authenticate on agency sites on your behalf. Those two statements come from the same vendor. Reading what a tool commits to in writing — the same exercise as working out where your files go when a tool processes them — tells you more than any security badge.
Hardening a contributor account without breaking uploads
A pass over contributor account security that separates what a second factor actually protects from what it does not: enabling 2FA where an agency documents it, identifying whether your upload credential is separate from your login, and auditing which credentials a third-party tool already holds. Items reflect each agency's published help pages.
When to turn it on, and what to do where you cannot
Where an agency documents 2FA and keeps the upload secret separate, turn it on today. Adobe is that case, and there is no automation cost to it. Where the agency couples the credentials, the second factor is not available to you anyway, so the protection has to come from elsewhere: a unique password per agency, a password manager rather than a reused string, and the discipline of rotating the password and the FTP client configuration in the same sitting rather than discovering the breakage at 3am.
Where nothing is published, check inside the account rather than guessing from the outside. Getty, iStock and Depositphotos may well offer a second factor in their signed-in settings; the absence of a public help article tells you about their documentation, not about their product. Fifteen minutes in your own account settings across five agencies produces a better inventory than any article can, including this one.
And treat the inventory as the deliverable. The useful artefact here is not a setting but a short list: for each agency, whether a second factor is on, which credential your pipeline holds, and whether those two are the same string. That list is what tells you, the next time an agency changes something, exactly which of your uploads is about to stop and which is unaffected.
For the record, since this article compares how others handle credentials: Rastock.ai delivers over FTP and SFTP to 10+ agencies, which means it holds agency delivery credentials like any tool in this category, and how those are stored and scoped is set out on its security page rather than summarised here. It takes no revenue share and claims no ownership of your files, and there is a 14-day trial with no card required if you want to check the credential handling against your own standards before committing anything.
Frequently asked questions
Does turning on 2FA break FTP uploads to stock agencies?
It depends on the agency, and the common claim that it never does is wrong. Adobe Stock has you generate a separate SFTP password in the Contributor Portal, so a second factor on your Adobe sign-in leaves the pipeline alone. Shutterstock's FTPS instructions and Alamy's FTP help both tell you to use your ordinary account password, which couples your login credential to your automation credential.
Does Shutterstock offer two-factor authentication for contributors?
Shutterstock does not document a user-enabled 2FA setting for contributor accounts on any of its public help pages. What it does document is a one-time passcode its security systems generate when a suspicious login attempt is detected, described as an additional layer of security rather than as two-factor authentication. That is risk-triggered rather than something you switch on.
Can I use an app-specific password for stock agency FTP?
None of Adobe, Shutterstock, Alamy, Getty Images, iStock or Depositphotos documents offering app-specific passwords. The closest real mechanism is Adobe's generate-a-password flow for SFTP in the Contributor Portal, which is functionally similar but is not described as an app password. Treat any advice to create one as unverified unless the agency itself documents it.
Do Getty Images and iStock support 2FA for contributors?
Not publicly answerable. The Getty Images contributor help centre sits behind a sign-in, so its account-security articles are not readable from outside, and the public iStock account FAQ covers only password rules and email-based reset. The correct reading is unknown rather than unavailable. Check your own signed-in account settings, since the public documentation will not confirm it either way.
Does 2FA protect the credentials I gave to a workflow tool?
No. A second factor guards the interactive sign-in, not a password already stored by a third party. If a tool holds your account password because its FTPS connection needs it, that credential lives in the vendor's storage and 2FA on the web login does not reach it. Credential handling by your tools is a separate decision from account security.
What is the safest setup across several agencies at once?
A unique password per agency held in a password manager, 2FA enabled wherever an agency documents it, and a written note of which credential each upload pipeline holds and whether it is the same string as the login. That inventory is what tells you which uploads will break when an agency changes something, rather than finding out when a batch fails overnight.