Shutterstock accepts contributor files over FTPS at ftps.shutterstock.com on port 21, using explicit TLS encryption and your ordinary contributor login. The transfer itself is all it does. Titles, keywords and categories still have to be added afterwards in the contributor dashboard before any of those files can go to review.
That last sentence is where most large uploads stall. FTP solves the slowest mechanical part of the job and leaves the part that takes judgement completely untouched. What follows is the setup exactly as Shutterstock documents it, the file rules that cause silent failures, and an honest look at what happens to the metadata once your files are sitting on the server.
Why FTPS beats the browser uploader
For ten files, the web uploader is faster. You drag, you wait, you are done. The case for FTPS starts somewhere around a hundred files, and it rests on three practical differences rather than on raw speed.
The first is file size. Through a browser you can send photos up to 50 MB and EPS files up to 100 MB. Over FTPS the JPEG and EPS caps stay the same, but TIFF files are accepted up to 4 GB. If you shoot large-format or panoramic work and want to keep a TIFF master in the pipeline, FTPS is the only route that will take it. Both sets of limits appear in Shutterstock's published technical requirements for images.
The second is video. Footage cannot be sent through any other channel — Shutterstock accepts video by FTPS or through the contributor web page only. Anyone mixing stills and clips ends up needing an FTPS client regardless of portfolio size.
The third is how the transfer behaves under stress. A desktop FTP client keeps a queue, retries a single failed file instead of failing the whole batch, and survives a dropped connection. A browser tab does none of that, and a four-hour upload that dies at ninety percent makes for a bad evening.
Setting up the FTPS connection
Shutterstock names three free clients in its own FTPS instructions: FileZilla, Cyberduck and WinSCP. The server details are identical across all three, and only the labels in the interface change.
FileZilla
- Protocol: FTP – File Transfer Protocol
- Host: ftps.shutterstock.com
- Port: 21
- Encryption: Use explicit FTP over TLS if available
- Logon Type: Normal
- User and Password: your Shutterstock contributor email address or username, and your account password
Connect, and expect a certificate warning on the first attempt. Shutterstock states plainly that this is normal behaviour: tick the option to always trust the certificate in future sessions and continue. If FileZilla offers to remember the password, decline on any machine you share with someone else.
Cyberduck
- Protocol: FTP-SSL (Explicit AUTH TLS)
- Server: ftps.shutterstock.com, port 21
- Username and password: the same contributor credentials, with Save Password left unchecked
WinSCP
- Protocol: FTP, with Encryption set to TLS/SSL Explicit Encryption
- Server: ftps.shutterstock.com, port 21, with your contributor username and password
One detail deserves more attention than the setup screens give it. The credential you are typing into that client is your live contributor account password, the same one that opens your earnings history and payout settings. Leaving it unencrypted in a desktop client's site manager is a habit worth breaking, and the same caution applies to any third-party tool that asks for those credentials.
File requirements that cause silent rejections
Files that break these rules do not always announce themselves at transfer time. They land on the server and fail later, which is why the rules are worth checking before the batch starts rather than after it finishes.
Format. JPEG and TIFF are both accepted, and JPEG is recommended because everything is converted to JPEG on approval anyway. Layered TIFFs and PSD files are not accepted at all. EPS files are accepted but must be saved in a format compatible with Adobe Illustrator 8 or 10. Still frames pulled from video are generally rejected on quality grounds, 8K source included.
Colour profile. Shutterstock serves images in sRGB. Anything submitted in another profile is converted on the way in, and that conversion will shift your colours, so convert before you upload rather than arguing with the result afterwards.
Dimensions. Every image must be at least 4 megapixels. Megapixels are width multiplied by height, not file weight in megabytes, and that single confusion produces a steady stream of rejections. Shutterstock's own worked examples make the line clear: 2000 by 2400 pixels is 4.8 MP and passes, while 1200 by 3000 pixels is 3.6 MP and is refused by the system before a reviewer ever sees it.
Vectors. EPS artwork has both a floor and a ceiling, no smaller than 4 MP and no larger than 25 MP, and the measurement comes from the bounding box around the artwork rather than the artboard behind it. A generous artboard with a small object sitting on it will still throw an error.
If you deliver to several agencies, be aware that the minimums are not identical everywhere, and the strictest of them should be the one setting your export preset.
Filenames carry more weight over FTP
In the browser you upload while looking at thumbnails. Over FTP you drop four hundred files into a folder and never see them again until they appear as rows in the contributor dashboard. At that point the filename is the only handle you have for matching a file to the metadata you wrote for it.
It is also how CSV metadata is matched, by exact filename. A consistent, sortable naming scheme stops being cosmetic the moment you move to bulk delivery.
The transfer finishes and the real work starts
Files sitting on Shutterstock's server are not submissions. Before anything reaches review, each one needs a description, keywords and a category, and the dashboard will not let you submit without them.
There are two ways to supply that. You can type it in the contributor interface, which is realistic for tens of files and punishing for hundreds. Or you can upload a CSV that maps filenames to descriptions, keywords and categories, which is the route almost every high-volume contributor arrives at eventually.
There is a third, quieter option: embed the metadata in the files themselves as IPTC and XMP fields before they ever leave your machine. Done properly, the description and keywords travel inside the JPEG, and you are no longer maintaining a separate spreadsheet that can drift out of sync with the folder it describes.
Where FTP stops scaling
FTP is a transfer protocol and it is very good at being one. The limits appear when you start asking it to be a workflow.
- It handles one agency at a time. A successful FTPS session with Shutterstock has done nothing for your Adobe Stock, Alamy or Pond5 queues. Each needs its own connection, its own metadata pass and its own conventions.
- There is no feedback channel. The client tells you the bytes arrived. It cannot tell you a file was refused for dimensions, or that half the batch is still sitting unsubmitted because the metadata never got attached.
- Duplicates are easy and expensive. Re-running a folder after an interrupted session is the standard way contributors end up with the same file twice in the same portfolio.
- Credentials accumulate. Every additional agency means another live account password stored in another desktop client's configuration file.
Delivering to Shutterstock alongside every other agency
This is the gap Rastock.ai was built to close. Instead of one FTP session per destination, files are processed once and delivered to 10+ agencies over FTP or SFTP — Adobe Stock, Shutterstock, Magnific, Alamy, Depositphotos, Pond5, Canva, 123RF, VectorStock and Vecteezy — with any other FTP-capable agency addable by hand.
The metadata is generated from the image itself — title, description and keywords — and then checked against each agency's rules rather than sent out identically everywhere. Banned and mandatory keyword lists are enforced per destination, and a bad batch can be rolled back instead of corrected file by file.
Two things it deliberately does not do: take a share of your earnings, or claim any ownership of your files. IPTC and CSV export stay open, so nothing you build inside it is locked in. There is a 14-day free trial with no card required, and the plans are listed openly.
If the multi-agency side is what you are weighing up rather than the Shutterstock connection specifically, the mechanics of automatic delivery are covered separately.
A workable FTP routine
- Export to sRGB JPEG at 4 MP or above, using a filename scheme you can sort and search six months from now.
- Write or generate the metadata before the transfer, either embedded in the files or held in a CSV keyed to those exact filenames.
- Transfer over FTPS with a client that queues and retries, and let it run unattended overnight.
- Reconcile in the dashboard the next morning: compare the count that arrived against the count you sent, attach the metadata, submit.
The routine works, and plenty of contributors have run it for years. It simply does not shrink as the portfolio grows, and that is usually the moment people start looking for something that does.
Frequently asked questions
What are the Shutterstock FTP server settings?
Shutterstock's FTPS server is ftps.shutterstock.com on port 21, using explicit FTP over TLS. Log in with your contributor email address or username and your account password. In FileZilla choose FTP with encryption set to explicit TLS; in Cyberduck choose FTP-SSL (Explicit AUTH TLS); in WinSCP choose FTP with TLS/SSL Explicit Encryption. A certificate warning on the first connection is expected behaviour.
Can I upload video to Shutterstock over FTP?
Yes, and for footage there is no real alternative. Shutterstock accepts video through FTPS or the contributor web page only, and FTPS is the practical choice when you are transferring several clips at once. The same server settings apply as for images. Metadata for clips is still added separately in the dashboard after the transfer completes.
Why did my file fail after a successful FTP transfer?
A completed transfer only means the bytes arrived. The usual causes of a later failure are dimensions below the 4 megapixel minimum, a colour profile other than sRGB, a layered TIFF or a PSD, or an EPS whose bounding box falls outside the 4 to 25 MP range. Files can also sit indefinitely without failing at all, because no metadata was attached and they were never submitted for review.
Does FTP upload add keywords automatically?
No. FTP moves files and does nothing else. Titles, keywords and categories are supplied separately: typed in the contributor dashboard, uploaded as a CSV keyed to filenames, or embedded in the files as IPTC and XMP fields before transfer. Tools that generate and deliver metadata alongside the files handle this step, but a plain FTP client never will.
Is FTP faster than the Shutterstock web uploader?
Not necessarily faster per file, but considerably more reliable for large batches. An FTP client queues files, retries individual failures and survives a dropped connection, whereas a browser upload of several hundred files can lose the entire session. FTPS also accepts TIFF files up to 4 GB, which the browser uploader will not take.