How to Upload Images to Adobe Stock via FTP: Complete 2026 Guide
Find your Adobe Stock FTP credentials, connect with FileZilla, upload in bulk and attach metadata correctly — plus the mistakes that lose files silently.
# How to Upload Images to Adobe Stock via FTP: Complete 2026 Guide
The Adobe Stock web uploader works fine for a handful of files. At a hundred it is tedious, and at a thousand it is unusable — browser sessions time out, transfers restart, and a single interruption costs you the batch. FTP is Adobe's supported route for bulk submission, and once configured it is both faster and more reliable.
This guide covers getting your credentials, connecting, transferring correctly, and the specific mistakes that cause files to vanish without an error message.
## Step 1: Get your FTP credentials
Your FTP details live in the Adobe Stock Contributor portal, not in your general Adobe account settings.
1. Sign in to the Adobe Stock Contributor portal.
2. Open the upload section.
3. Locate the FTP details panel.
You will need three things: the **host address**, your **user name**, and an **FTP password**.
The important detail is that the **FTP password is separate from your Adobe account password**. It is generated inside the portal specifically for FTP access. If you try to connect with your normal Adobe credentials, authentication fails — this is the single most common setup problem.
## Step 2: Connect with an FTP client
Any standard FTP client works. FileZilla is the common choice because it is free, cross-platform and handles large queues well.
In FileZilla, open Site Manager and create a new site:
- **Host**: the address from the contributor portal
- **Protocol**: FTP
- **Logon Type**: Normal
- **User**: your contributor user name
- **Password**: the FTP password generated in the portal
Connect. You should land in your contributor directory.
### Transfer settings that matter
Set the transfer type to **binary**, not ASCII or auto. Image files transferred in ASCII mode become corrupted and are silently discarded. In FileZilla this is under Transfer settings; binary is safest for a queue that contains only images.
Keep concurrent transfers modest — four to eight simultaneous connections is plenty. Pushing dozens in parallel tends to trigger throttling and produces more failed transfers than it saves in time.
## Step 3: Upload to the root directory
Drop your files into the **root of your contributor directory**. Do not create subfolders.
This trips up a lot of people who organise their local work into folders by shoot or date and mirror that structure on the server. Adobe's ingest process looks at the root. Files sitting inside `/2026-summer/` are not picked up, and you get no error telling you so — they simply never appear in the portal.
Organise locally however you like. On the server, everything goes in the root.
## Step 4: Embed metadata before you transfer
This is where Adobe differs from Shutterstock. Shutterstock lets you attach a CSV after upload to apply titles and keywords in bulk. **Adobe does not.** Adobe reads **IPTC metadata embedded inside the file itself**.
That means your titles, descriptions and keywords need to be written into the image before it leaves your machine. Once the file is on Adobe's server, editing metadata means going through the portal file by file — which defeats the purpose of bulk uploading in the first place.
Practically:
- Embed IPTC title, description and keywords locally
- Verify with any metadata viewer that the fields are actually written
- Only then transfer
Adobe accepts up to **49 keywords** and weights the first ten most heavily, so order matters. Our guide to [writing metadata for stock photos](/blog/how-to-write-metadata-for-stock-photos) covers the fields in detail, and [choosing keywords that convert](/blog/best-keywords-for-stock-photos) covers ordering and research.
## Step 5: Wait, then verify in the portal
Files do not appear instantly. After a transfer completes, Adobe's ingest process picks them up and they surface in the portal's unsubmitted queue. This can take minutes or considerably longer during busy periods.
Once they appear, check that metadata came through. If titles and keywords are blank, the IPTC embedding did not work and it is worth fixing the process before uploading another batch — otherwise you will be re-keywording hundreds of files by hand.
Then submit for review from the portal. FTP delivers files; it does not submit them.
## Common problems and what causes them
**Files transferred but never appeared.** Almost always a subfolder. Move them to the root.
**Corrupted or rejected files.** ASCII transfer mode. Switch to binary and re-upload.
**Authentication failed.** Using the Adobe account password instead of the FTP-specific password from the portal.
**Metadata missing after upload.** IPTC was not embedded, or was written to a field Adobe does not read. Verify locally before transferring.
**Transfer stalls on large batches.** Too many concurrent connections, or an unstable connection with no resume. FTP can resume; make sure your client is configured to.
## Automating the whole pipeline
FTP solves the transfer problem. It does not solve the metadata problem — and at volume, metadata is the real bottleneck. Writing a title, description and up to 49 keywords for every file by hand takes five to twenty minutes each. For a 500-file batch that is weeks of work, and FTP just means you deliver the backlog faster.
This is the gap automation fills. Rastock AI [generates metadata, embeds it as IPTC, and delivers over FTP](/features) to Adobe Stock and 25+ other agencies in one pass, so the file that lands on Adobe's server already carries correct, agency-formatted metadata. Our guide to [automating stock photo uploads](/blog/ai-metadata-generator-for-stock-photos) covers the broader workflow, and plans by upload volume are on the [pricing page](/pricing).
## Summary
FTP is straightforward once the three non-obvious details are handled: use the portal-generated FTP password, transfer in binary, and upload to the root with no subfolders. Embed IPTC metadata before transferring, because Adobe has no CSV fallback. Then verify in the portal before submitting.
Done properly, a batch that took a full day through the web uploader becomes a background transfer you start and walk away from.
This guide is part of our overview of [where to sell stock photos](https://rastock.ai/blog/where-to-sell-stock-photos), which compares every major agency on royalties, review standards and AI policy.
For the full picture, see our guide to the [stock photography workflow](https://rastock.ai/blog/stock-photography-workflow) — every stage from selection through metadata to delivery.
## Related reading
- [Shutterstock CSV Template: Download + How to Use It](https://rastock.ai/blog/shutterstock-csv-template)
- [Bulk Uploading to Vecteezy: FTP Delivery and Batch Metadata](https://rastock.ai/blog/vecteezy-bulk-ftp-strategy)
- [Free Metadata Generator for Adobe Stock: How It Works](https://rastock.ai/blog/free-metadata-generator-for-adobe-stock)
Frequently asked questions
Where do I find my Adobe Stock FTP credentials?
Log in to the Adobe Stock Contributor portal and open the upload section. FTP details are shown there: the host address, your user name and a password specific to FTP. The FTP password is separate from your Adobe account password and is generated in the portal.
What FTP client works with Adobe Stock?
Any standard client works. FileZilla is the usual choice because it is free and cross-platform. Enter the host, your contributor user name and the FTP password from the portal, then transfer files into the root directory rather than creating subfolders.
Why don't my FTP uploads appear in Adobe Stock?
The most common causes are uploading into a subfolder instead of the root, transferring in ASCII rather than binary mode, or an interrupted transfer leaving a partial file. Files also take time to appear in the portal after transfer completes — they are not instant.
Can I upload metadata with FTP to Adobe Stock?
Adobe reads IPTC metadata embedded inside the file, so titles and keywords travel with the image over FTP. Adobe does not use a separate CSV attachment the way Shutterstock does, which makes embedding metadata before transfer the reliable approach.
How many files can I upload to Adobe Stock at once?
There is no hard per-batch cap on FTP transfer itself, but Adobe applies review quotas and very large simultaneous batches slow the review queue. Uploading in batches of a few hundred, with metadata already embedded, is more predictable than pushing thousands at once.
Is FTP better than the Adobe Stock web uploader?
For more than a handful of files, yes. FTP resumes interrupted transfers, handles large batches without a browser session, and can be automated. The web uploader is simpler for occasional submissions but becomes the bottleneck at volume.