Most contributors assume one upload protocol covers every agency. It does not. Adobe Stock accepts SFTP on port 22, Shutterstock accepts FTPS on port 21 with explicit TLS, and Alamy, Depositphotos and 123RF still accept plain FTP. Choosing the wrong one rarely produces a useful error message — it produces a connection that simply never opens.
The three protocols that all get called "FTP"
The confusion is baked into the names. Agencies, forums and even some upload tools use "FTP" as a catch-all for any credentialed file transfer, but there are three distinct protocols hiding behind that word, and they are not variations on a theme.
- FTP is the original protocol. The client opens a control connection on port 21 and the two sides then negotiate a second, separate connection for the file data itself. Nothing is encrypted: the username, the password and the file contents all cross the network in the clear.
- FTPS is that same protocol with TLS added. It comes in two flavours. Explicit FTPS connects on the normal port 21 and then issues an AUTH TLS command to upgrade the session. Implicit FTPS expects TLS from the very first byte, usually on a dedicated port. The distinction matters because a client set to the wrong flavour fails during the handshake, not at login.
- SFTP is not FTP in any meaningful sense. It is a file-transfer subsystem that runs inside an SSH session on port 22. One connection, one port, and the server is authenticated by a host key rather than a certificate chain. It shares a name with FTP and almost nothing else.
The practical consequence is that a client configured for FTP will never reach an SFTP host, and a client configured for SFTP will never reach an FTPS host. In FileZilla, Cyberduck or WinSCP the two dialogue boxes look nearly identical — same host field, same username, same password — so the mistake is easy to make and the symptom is always the same unhelpful timeout.
What the major agencies actually accept
There is no industry convention here. The two largest agencies have landed on opposite answers: Adobe Stock publishes an SFTP endpoint at sftp.contributor.adobestock.com on port 22, while Shutterstock's own contributor help documentation specifies FTPS at ftps.shutterstock.com on port 21, with FileZilla set to "Use explicit FTP over TLS if available" and the equivalent explicit-TLS setting in Cyberduck and WinSCP. Both are secure. Neither will talk to the other's client configuration.
Delivery protocol by agency
Protocol, port, remote path and the per-agency catch for ten stock agencies that accept credentialed delivery, plus three that do not. Adobe Stock uses SFTP on port 22, Shutterstock uses FTPS on port 21 with explicit TLS, and several agencies still run plain FTP on port 21.
Those two hostnames are worth writing down because they are published and stable. For the rest of the list, take the host from your own contributor portal rather than from a third-party article. A wrong hostname is the one configuration error that produces no diagnostic at all, and agencies do change endpoints without announcing it.
The port number is not something you can infer
The convention — 21 for FTP and FTPS, 22 for SFTP — holds often enough that most upload tools simply derive the port from the protocol you picked. Magnific, the agency formerly known as Freepik, breaks it: its SFTP endpoint runs on port 60022. If your tool fills the port in for you based on the protocol, it will try 22, get nothing, and report a connection failure that looks exactly like a wrong password. Any pipeline that stores per-agency presets needs to treat the port as part of the preset, not as something computed from the protocol type.
Passive mode, firewalls and the second connection
This is where FTP and FTPS cost you time that SFTP never does. Both open a second connection for the file data, and there are two ways to decide who opens it. In active mode the server connects back to the client, which almost never survives a home router or a corporate firewall. In passive mode the client opens both connections, which is why passive is the default in every modern client.
Some agencies require it explicitly. VectorStock's batch endpoint will not complete a transfer unless the client is in passive mode, and because the control connection succeeds first, the failure shows up as a directory listing that hangs rather than as a login error. FTPS adds one more wrinkle: the data channel has to negotiate TLS separately from the control channel, and a NAT device that rewrites the control traffic can leave the two out of step.
SFTP has none of this. Everything — commands, directory listings, file bytes — travels inside the single SSH connection on port 22. On a restrictive network that is the difference between a pipeline that runs and a pipeline you spend an evening debugging. If a transfer is stalling rather than failing outright, the diagnosis is usually the data channel; the symptoms are covered in more detail in our guide to FTP uploads that stall halfway.
Your transfer password is not always your account password
Agencies split three ways on credentials, and guessing wrong here will lock you out of your own account if you retry enough times.
- Adobe Stock issues separate transfer credentials from the Contributor portal, under Upload. They are not your Adobe ID password, and typing the Adobe ID password into an SFTP client will simply fail.
- Shutterstock uses your contributor email address or username together with your contributor account password. Its help page also suggests leaving the client's "save password" box unchecked, which is sensible advice for a credential that is also your account login.
- 123RF uses your 123RF account password directly. Combined with plain FTP, that means your account password crosses the network unencrypted on every upload — a good reason not to reuse it anywhere else.
One more Adobe-specific quirk is worth knowing before you plan a pipeline around it: the SFTP option does not appear for every contributor. When it vanished from a number of accounts, Adobe's technical support told contributors that only qualified accounts can use it, without publishing the criteria. If the option is not in your portal, the portal upload is the documented route and there is nothing to configure.
Where the file lands matters as much as how it got there
Most agencies drop everything in the root directory and sort it out at the portal. Alamy does not. The remote folder you choose is part of the submission: Stock is the general commercial collection, while Live News and Archive stock require prior approval before anything you put there will be processed, and Vectors is separate again. Alamy also asks that a first submission be three images only, so a first run that pushes a whole batch is the wrong way to start. The agency-specific sequence is in our Alamy upload workflow walkthrough.
Two other agencies attach conditions to the delivery itself. Magnific does not process anything until you return to the contributor portal and press Synchronize FTP, so a transfer that completed successfully can still look like it was ignored. VectorStock accepts only ZIP archives in a flat structure, up to 4 GiB, each EPS paired with a matching JPG of at least 1000 pixels carrying embedded keywords, and AI artwork filenames have to begin with vsai. The full archive layout is covered in the VectorStock upload workflow guide.
What one multi-agency delivery run looks like
The five stages of a single delivery run across agencies on different protocols, from reading each agency's protocol, port and remote path out of its own portal through to the post-upload step that Magnific requires before files are processed.
The agencies that do not take credentialed delivery at all
Planning a pipeline means knowing where the pipeline stops. PIXTA no longer accepts FTP delivery, and since 20 April 2026 it has not accepted AI-generated content at all, so for a portfolio built around generative work it is off the list twice over. Creative Market is a marketplace with portal upload only. Storyblocks has no confirmed contributor transfer endpoint; its documented route remains the portal. Treating any of these as an FTP target is how a batch silently goes nowhere.
Getty Images deserves a specific warning because searching for its transfer settings leads to the wrong product. The SFTP endpoint that turns up in Getty's documentation belongs to Media Manager, an enterprise digital asset management system where you create your own credentials under bulk management. That is not contributor submission. Getty's contributor route runs through its Enterprise Submission Portal, which has its own separate settings. Pointing a contributor batch at the Media Manager host will fail, and it will fail in a way that looks like an account problem rather than a configuration one.
Choosing between them when the agency gives you a choice
A handful of agencies accept more than one protocol, VectorStock among them. When you have the choice, take SFTP. It uses one connection on one port, so there is no data channel to negotiate and nothing for a firewall or a NAT device to break halfway through. It authenticates the server with a host key, which your client can pin and then warn you about if it ever changes. And it keeps credentials and file bytes inside the same encrypted session rather than upgrading a plaintext protocol after the fact.
Explicit FTPS is a perfectly reasonable second choice, and when an agency specifies it there is nothing to debate — set the client to explicit TLS and move on. Plain FTP is the one worth treating as a constraint rather than an option. If an agency offers nothing else, use it, but give that account a password you use nowhere else, and do not let a client save it on a shared machine. The protocol was designed in an era before any of this mattered, and no amount of configuration changes what it sends in the clear.
What this means for a multi-agency pipeline
Deliver to one agency and the protocol is a setting you configure once and forget. Deliver to ten and it becomes four variables per agency — protocol, port, remote path and whatever has to happen after the transfer — none of which can be inferred from the others. That is the real answer to the FTP versus SFTP question for contributors: you do not choose one, you record both correctly per destination. The step-by-step versions for the two largest agencies are in our Shutterstock FTP upload guide and the walkthrough for uploading to Adobe Stock over FTP.
Keeping that straight by hand is where most contributors eventually stop expanding their distribution. Rastock.ai stores the protocol, port, path and post-upload step per agency and delivers to 10+ agencies over FTP, FTPS or SFTP using your own credentials, with any other agency that accepts credentialed delivery addable by hand. It generates the metadata too, exports IPTC and CSV freely, takes no share of your royalties and claims no ownership of your files. You can see how it fits a delivery pipeline or start on the 14-day free trial from the pricing page — no card required.
Frequently asked questions
Is SFTP just FTP with encryption added?
No. FTPS is FTP with encryption added — the same protocol with TLS layered on, still on port 21. SFTP is a different protocol entirely: a file-transfer subsystem inside an SSH session on port 22. They share three letters and almost nothing else, which is why a client configured for one will never connect to the other.
Which protocol does Adobe Stock use for contributor uploads?
Adobe Stock uses SFTP on port 22, at sftp.contributor.adobestock.com, with credentials generated in the Contributor portal rather than your Adobe ID password. The option is not visible on every account: when it disappeared for a number of contributors, Adobe support said only qualified accounts can use it, without publishing the criteria. Otherwise the portal upload is the documented route.
Which protocol does Shutterstock use?
Shutterstock uses FTPS, not SFTP. Its contributor help documentation specifies ftps.shutterstock.com on port 21 with explicit TLS — in FileZilla that is "Use explicit FTP over TLS if available", and the equivalent explicit-TLS settings in Cyberduck and WinSCP. A certificate warning on the first connection is expected and can be accepted. Login is your contributor email or username.
Why does my upload connect but then hang?
That pattern almost always means the control connection succeeded and the data connection did not, which only happens on FTP and FTPS. Switch the client to passive mode: VectorStock requires it outright, and most firewalls block the server-initiated connection that active mode needs. SFTP cannot fail this way because it carries everything over the single port 22 connection.
Can I assume port 21 for FTP and port 22 for SFTP?
Usually, but not always, and the exception is costly. Magnific, formerly Freepik, runs SFTP on port 60022. A tool that derives the port from the protocol will try 22, get nothing, and report what looks like a credential error. Store the port as part of each agency's settings rather than computing it from the protocol type.
Do all stock agencies accept FTP delivery?
No. PIXTA no longer accepts it, and has not accepted AI-generated content since 20 April 2026. Creative Market is portal upload only. Storyblocks has no confirmed contributor transfer endpoint. Getty's contributor route runs through its Enterprise Submission Portal, which is separate from the Media Manager SFTP endpoint that its enterprise documentation describes.