Adobe Stock + Xpiks ◇ Qualified
Only qualified Adobe Stock contributor accounts receive SFTP credentials. Xpiks can use those credentials for upload, but that does not establish automated final submission for moderation.
Stock submission route reference · Draft · not launch-ready
Stock agency submission routes
Tool support, status & native fallbacks
A source-linked, last-checked matrix for Shutterstock, Adobe Stock, Pond5 and Getty/iStock, including StockSubmitter, Microstock+ and Xpiks where public evidence supports a route, limitation, unknown or conflict.
Reference key
Status
Supported
Current public first-party support with no material in-scope contradiction.
Qualified
Available only under a visible account, credential, media, version, plan or workflow condition.
Conflicting
Current in-scope sources materially disagree.
Unsupported
Current first-party tool or agency source explicitly says unavailable.
Unknown
Evidence is insufficient, ambiguous, stale, private or account-specific.
Supported ≠ guaranteed. A documented route can still vary at runtime or by account. Material publicly documented eligibility or workflow conditions are labeled Qualified.
Upload ≠ final submission. Tool support does not necessarily establish submit-for-review automation.
Uncertainty ≠ failure. Conflicting does not mean broken, and Unknown does not mean unsupported.
Submission-route matrix
Choose an agency. Follow the route.
Read each route from state to workflow boundary, then use the native fallback and linked evidence when a third-party route is limited, uncertain or disputed.
01
Shutterstock
Native web, FTPS and mobile upload are publicly documented. Upload and final submission remain distinct workflow stages.
| Route | State | Route / limitation | Upload → submit boundary | Native fallback | Evidence |
|---|---|---|---|---|---|
| Route Native Agency baseline | Supported Current Shutterstock contributor documentation establishes web, FTPS and mobile routes plus the preparation-before-review workflow. | Web, FTPS and Contributor mobile-app upload. | After upload, titles, keywords, categories and releases are prepared before submission for review; the mobile app can also submit images for review. | — | Checked |
| Route StockSubmitter | Supported StockSubmitter lists Shutterstock among supported agencies, separately identifies upload-only agencies, and defines submission as filling metadata and sending the file for review automatically. | Vendor currently lists Shutterstock among agencies with submissions. | StockSubmitter publicly claims automated submission: after upload, it fills metadata fields and sends the file for review automatically. This is a vendor capability claim, not an account-level runtime guarantee. | Native web / FTPS / mobile | Checked |
| Route Microstock+ | Supported Current first-party Microstock+ supported-agency and workflow documentation establishes the public support claim. | Vendor currently lists Shutterstock among supported agencies and provides submission allotments for it. | Microstock+ documents automatic submission after a successful upload; this remains a vendor capability claim rather than an account-level guarantee. | Native web / FTPS / mobile | Checked |
| Route Xpiks | Supported Xpiks says it can upload to any agency supporting FTP/FTPS/SFTP, and Shutterstock publicly supports contributor FTPS upload. | FTPS upload via Xpiks to Shutterstock. | Xpiks establishes file upload over FTPS; it does not establish automated final submission for review. | Native web / FTPS / mobile |
|
02
Adobe Stock
Contributor Portal is the ordinary native route. SFTP is an additional route available only to qualified contributor accounts.
| Route | State | Route / limitation | Upload → submit boundary | Native fallback | Evidence |
|---|---|---|---|---|---|
| Route Native Agency baseline | Supported Adobe publicly documents Contributor Portal submission and separately documents SFTP qualification. | Contributor Portal; SFTP additionally available to qualified contributors. | The Contributor Portal workflow includes upload, metadata and submission for moderation. SFTP is an alternate upload transport for qualified accounts, not a bypass of the submission workflow. | Contributor Portal |
|
| Route StockSubmitter | Supported StockSubmitter lists Adobe Stock among agencies with submissions, separately identifies upload-only agencies, and defines submission as filling metadata and sending the file for review automatically. Adobe SFTP documentation corroborates one qualified upload transport, not the final-submit implementation. | Vendor currently lists Adobe Stock among agencies with submissions. Adobe separately documents StockSubmitter as an example third-party tool for qualified SFTP upload. | StockSubmitter publicly claims automated submission for Adobe Stock: after upload it fills metadata fields and sends the file for review automatically. This is a vendor capability claim, not an account-level runtime guarantee. | Contributor Portal | Checked |
| Route Microstock+ | Supported Current first-party Microstock+ documentation lists AdobeStock among submission-supported agencies, documents AdobeStock account activation, and documents automatic submission after successful upload. | Vendor currently lists Adobe Stock among agencies with submissions. AdobeStock activation in Microstock+ may require completing Adobe's account-authentication challenge by SMS or email. | Microstock+ documents automatic submission after a successful upload, including filling metadata and sending the file for agency review. This remains a vendor capability claim rather than an account-level guarantee. | Contributor Portal |
|
| Route Xpiks | Qualified Xpiks and Adobe both document the qualification requirement for Adobe SFTP access. | Adobe upload credentials can be configured only where Adobe grants the contributor SFTP qualification. | Qualified SFTP upload is documented; final submit-for-review behavior is not inferred from the file-transfer route. | Contributor Portal | Checked |
03
Pond5
Native upload is followed by metadata editing and explicit submission for review. Tool claims and user reports can therefore disagree without proving global failure.
| Route | State | Route / limitation | Upload → submit boundary | Native fallback | Evidence |
|---|---|---|---|---|---|
| Route Native Agency baseline | Supported Current Pond5 selling documentation establishes the native workflow. | HTML5 or FTP upload. | Upload is followed by metadata editing and an explicit Save and Submit for Review step. | — |
|
| Route StockSubmitter | Conflicting StockSubmitter first-party documentation claims Pond5 submission support; Pond5-hosted affected-user evidence documents a working upload path but a blocked final-submit step, with fresher Pond5 reporting also saying the prior workflow no longer works. | StockSubmitter currently lists Pond5 among agencies with submissions, while affected-user evidence documents Pond5 upload succeeding but automated final submission failing. | StockSubmitter currently claims automated Pond5 submission. A Pond5 contributor report documents successful StockSubmitter upload but failure at the final submission stage because of Pond5's CAPTCHA. The current sources therefore conflict about whether automated final submission works. | Native Pond5 HTML5 / FTP upload |
|
| Route Microstock+ | Qualified Current first-party Microstock+ documentation establishes the Pond5 route and its extension, Freestock and signed-in Chrome-profile conditions. | Vendor documents a Pond5 browser-extension route that requires a supported extension version, Freestock running, and Microstock+ and Pond5 signed in within the same Chrome profile. | The extension documentation says it uploads the file, fills metadata and releases when supplied, and performs the final Pond5 submit step. | Native Pond5 HTML5 / FTP upload | Checked |
| Route Xpiks | Supported Xpiks says it can upload to any agency that supports FTP/FTPS/SFTP, and Pond5 publicly supports contributor FTP upload. | FTP upload via Xpiks to Pond5. | Xpiks establishes FTP file upload; it does not establish automated final submission for review. Pond5 requires a separate metadata/editing and Save and Submit for Review stage. | Native Pond5 HTML5 / FTP upload |
|
04
Getty / iStock
Public contributor material establishes website contribution, while detailed private ESP mechanics remain intentionally outside the native claim.
| Route | State | Route / limitation | Upload → submit boundary | Native fallback | Evidence |
|---|---|---|---|---|---|
| Route Native Agency baseline | Supported Current public Getty contributor material establishes the narrow website-contribution and accepted-contributor upload claim. | Official website contribution route; accepted contributors can submit from desktop or mobile. | Public Getty material establishes website contribution and accepted-contributor desktop/mobile submission; detailed private ESP mechanics remain outside the claim. | Official Getty / iStock contributor route | Checked |
| Route StockSubmitter | Conflicting Current first-party StockSubmitter and Microstock+ sources materially disagree about whether automated iStock ESP submission through StockSubmitter remains available. | StockSubmitter currently claims automated iStock ESP submission, while Microstock+ documentation says an iStock protection change made submission through both M+ and StockSubmitter impossible. | StockSubmitter currently claims automated iStock ESP submission. Microstock+ documentation says an iStock protection change made submission through StockSubmitter impossible. Its documented Chrome-extension workaround does not explicitly establish that StockSubmitter itself now uses the workaround. The current sources therefore conflict about automated final submission. | Official Getty / iStock contributor route |
|
| Route Microstock+ | Qualified Current first-party Microstock+ documentation establishes support with explicit browser-extension and signed-in-session conditions. | Vendor lists iStock ESP support and documents a Chrome-extension workaround required after iStock protection changes. | The extension guide says keywording, uploading and submitting should work after setup; the browser and authenticated ESP tab must remain open during the workflow. | Official Getty / iStock contributor route | Checked |
| Route Xpiks | Unsupported Current first-party Xpiks documentation explicitly says direct Getty / iStock upload is unavailable. | Xpiks explicitly says it does not directly upload to Getty / iStock; it can prepare metadata and points contributors to DeepMeta or qHero for upload. | Direct Xpiks upload is unsupported, so a direct Xpiks final-submit boundary is not applicable. | Official contributor route; Xpiks names DeepMeta or qHero as specialist upload workflows |
|
Conflict & qualification notes
Uncertainty is part of the answer.
Pond5 + StockSubmitter ↔ Conflicting
StockSubmitter still publicly claims automated Pond5 submission. A Pond5 contributor report documents successful StockSubmitter upload but failure at final submission because of Pond5's CAPTCHA; a fresher Pond5 report says the prior upload-and-submit workflow no longer works. The unresolved disagreement remains Conflicting.
Pond5 + Microstock+ ◇ Qualified
The route requires a supported Microstock+ extension version, Freestock running, and Microstock+ and Pond5 signed in within the same Chrome profile.
Getty / iStock + StockSubmitter ↔ Conflicting
StockSubmitter still publicly claims automated iStock ESP submission, while Microstock+ says iStock protection blocked submission through both M+ and StockSubmitter. The Microstock+ guide documents a Chrome-extension workaround, but does not explicitly establish that the workaround restores StockSubmitter itself, so this row remains Conflicting rather than Qualified.
Getty / iStock + Microstock+ ◇ Qualified
Microstock+ says direct M+/StockSubmitter submission was blocked by a newer iStock protection system and documents a Chrome-extension workaround. The extension, open browser and authenticated ESP session are therefore material workflow conditions.
Sources & method
How status is assigned
- 01Agency documentation
Governs native agency routes and workflow stages.
- 02Tool documentation
Governs what a tool publicly claims about its own support and workflow.
- 03Affected-user reports
Can create or maintain a conflict, but cannot alone establish global support or failure.
- 04Specialist articles
Can add context or surface conflicts, but do not outrank current first-party route-state sources.
- 05Incomplete public evidence
Incomplete public first-party evidence resolves to Unknown rather than a guess. Where public first-party evidence establishes a route but documents a material visible eligibility or workflow condition, the route is Qualified. Private or account-connected verification is not used by this reference.
Reference policy
A dated reference, not a real-time status service.
Submission workflows change. Rows are manually reviewed against public sources once each calendar month, targeting roughly 30 days between successful source checks, with material route changes eligible for an earlier review.
One designated content/source owner is responsible for the review cycle. Each review records the source URL, check date, material change or no-change, resulting state, and owner role.
Supported or Qualified rows cannot remain more than 45 days after their last successful source check. If verification becomes overdue, the row is downgraded to Unknown with a visible verification-overdue note until rechecked.