A stock tool can reach your agency accounts in three ways, and they are not equivalent. It can use an upload credential the agency issues separately, it can ask for your actual account login, or it can distribute under its own accounts and pay you a share of what sells. The first is the safest, because those credentials are scoped to uploading and can be regenerated without touching your account password.
The question comes up constantly, and it deserves a more careful answer than “trust the vendor”. What you are handing over differs by tool, the blast radius if something goes wrong differs by model, and only one of the three lets you cut access off cleanly and instantly.
The three access models
1. An agency-issued FTP or SFTP credential
Most agencies that accept bulk uploads hand out a dedicated upload credential that is not your website login. Adobe Stock is the clearest example: qualified contributor accounts can generate an SFTP username and password from inside the contributor portal, and generating a new one replaces the previous pair. That single behaviour is what makes this model safe — revoking access is one click, and it does not disturb the password you sign in with.
Not every agency separates the two cleanly. Xpiks maintains a setup guide covering agency credentials that is useful precisely because it documents the differences: Adobe issues a generated SFTP pair, Dreamstime gives a different FTP username but keeps the same password as your account login, and 123RF surfaces credentials in the upload area. Where the password is shared with the account login, the credential is no longer revocable in isolation.
It is also worth knowing what an upload credential does and does not grant. It writes files into an intake folder. It does not read your sales figures, change your payout details, edit your live portfolio or delete anything already accepted. That narrow scope is the whole argument for this model.
2. Your full account login
Some tools ask for the email and password you use to sign in, usually because they automate the web interface rather than talking to an upload endpoint. This is a different level of exposure. A session that can sign in as you can, in principle, reach earnings pages, payout settings, portfolio edits and account-level actions — and if you use that password anywhere else, the exposure follows you off the platform.
There are legitimate tools in this category, and asking for a login is not evidence of bad intent. But it removes your ability to revoke selectively: the only way to cut access is to change the password, which breaks every other device and tool at the same time. If you go this route, use a password unique to that agency and enable two-factor authentication where the agency offers it.
3. Managed distribution, where you hand over no credential at all
The third model sidesteps credentials entirely. You upload to the platform, it distributes to its agency partners on your behalf, and it takes a commission on what sells. Wirestock is the best-known example; its own contributor guidelines describe the commission model directly. From a pure account-security standpoint this is the cleanest arrangement: there is nothing to leak, because you never issued anything.
The trade is elsewhere. Your work sells through the platform's relationship rather than your own contributor account, the commission is permanent for the life of those files, and leaving means untangling what was distributed where. That is a business decision rather than a security one, and we covered it separately in stock tools that don't take a revenue share.
What each tool actually asks for
Vendors describe this differently, so it helps to line them up by what they need rather than by how they market themselves. Where a detail is not documented publicly, it is described here in general terms rather than guessed at.
Xpiks
- Asks for: agency FTP or SFTP credentials, entered once per agency.
- Where they live: on your own machine, since Xpiks is a desktop application rather than a hosted service.
- Strength: nothing leaves your computer except the upload itself, and the setup guide is unusually explicit about where each agency's credentials come from.
- Limitation: local storage also means local responsibility — a compromised laptop is a compromised credential set, and there is no central place to revoke.
StockSubmitter
- Asks for: per-agency upload credentials, configured inside the desktop app.
- Strength: very broad agency coverage, and long-standing familiarity among high-volume contributors.
- Limitation: same desktop trade-off — the machine running it becomes the security boundary, and it has to be switched on for a batch to go out.
PhotoTag.ai
- Asks for: nothing from your agency accounts. It generates keywords and titles and hands the files back.
- Strength: the lowest-exposure option by definition — no credential is involved at any point.
- Limitation: it solves half the job. Delivery, per-agency field mapping and upload status remain manual.
Wirestock
- Asks for: no agency credentials. You upload to Wirestock and it distributes to its partner agencies.
- Strength: genuinely hands-off, keywording included, and no credential to protect or rotate.
- Limitation: a commission applies to sales, and the agency relationship belongs to the platform rather than to you.
Rastock AI
- Asks for: the agency-issued FTP or SFTP credential for each agency you want to deliver to — the revocable kind, not your account login.
- Strength: metadata and delivery in one pass to 10+ agencies, with per-file status, no revenue share, no ownership claim, and IPTC and CSV export left open so you can walk away with everything.
- Limitation: it is a hosted service, so the credentials sit with a vendor rather than only on your laptop. If your rule is that nothing leaves your machine, a desktop tool fits you better.
When to use which
Use a desktop tool when your working rule is that credentials never leave hardware you control, your upload volume fits into sessions where the machine is on anyway, and you are comfortable being your own backup and recovery plan. Xpiks and StockSubmitter both fit that profile well.
Use a hosted pipeline when batches run overnight or from more than one machine, when you need delivery status you can check the next morning without the laptop being awake, and when you want per-agency rules applied before delivery rather than discovered at moderation. The trade you are making is explicit: convenience and continuity in exchange for a vendor holding a revocable upload credential.
Use managed distribution when you would rather not deal with agency accounts at all and accept a commission as the price of that. And use a metadata-only tool when your uploading already works and the bottleneck is purely writing titles and keywords.
The one combination worth avoiding is handing your primary account login to any of them. If a tool cannot work with the credential an agency issues for uploading, that is a design decision on their side, and it is a fair reason to look elsewhere.
A checklist before you paste a password anywhere
- Generate the upload credential from inside the agency's own portal, not from a link a tool sent you.
- Confirm it is separate from your sign-in password. If the agency reuses your account password for FTP, treat the credential as account-level and act accordingly.
- Prefer SFTP over plain FTP wherever the agency offers it, since plain FTP sends credentials unencrypted.
- Test with a small batch before pointing a tool at a full archive, and check what actually landed in the agency's intake.
- Know how you would revoke it today. If the answer is "change my account password", you are on the wrong access model.
- Regenerate credentials when you stop using a tool. Uninstalling it does not invalidate what it already holds.
If you have never generated an upload credential before, our walkthrough of uploading to Adobe Stock over FTP covers the portal steps end to end.
Where this leaves you
Give tools the credential the agency issues for uploading, keep your account login to yourself, and choose between local and hosted based on how you actually work rather than on which sounds safer in the abstract. Rastock AI sits in the hosted category deliberately: it takes the revocable upload credential, writes agency-compliant metadata, delivers to 10+ agencies and shows you what landed. You can look at the delivery and status pipeline or start on the 14-day free trial without a card.
Frequently asked questions
Is it safe to give a stock tool my agency FTP password?
It is the safest of the available options, provided the agency issues that credential separately from your account login. Adobe Stock, for example, generates an SFTP username and password inside the contributor portal, and generating a new pair replaces the old one. The credential writes files into an intake folder; it cannot read earnings, change payout details or edit your live portfolio.
Should I ever give a tool my stock account login?
Avoid it where you can. A full login can, in principle, reach earnings pages, payout settings and account actions, and the only way to revoke it is to change the password, which breaks every other tool and device at once. If a tool requires it, use a password unique to that agency and turn on two-factor authentication if the agency supports it.
How do I revoke a tool's access to my stock account?
If you used an agency-issued upload credential, generate a new one in the contributor portal. That invalidates the pair the tool holds without affecting your sign-in. If you handed over an account login, you have to change the account password instead, and then reconnect everything else that used it. Uninstalling a tool does not revoke anything on its own.
Is a desktop tool safer than a hosted service?
It is different rather than strictly safer. A desktop tool keeps credentials on hardware you control, which removes vendor risk but makes your machine the single point of failure and requires it to be running for uploads to go out. A hosted service holds a revocable credential and keeps batches running unattended. Match the model to how you actually work.
What is the difference between FTP and SFTP for stock uploads?
Plain FTP transmits your credentials and files without encryption, so anyone able to observe the connection can read them. SFTP encrypts the session. Where an agency offers both, choose SFTP. Adobe Stock issues SFTP credentials to qualified contributor accounts, and most tools that support FTP support SFTP as well.
Do managed distribution platforms need my agency accounts?
No. Platforms like Wirestock distribute under their own agency relationships, so there is no credential to hand over. The trade-off sits elsewhere: their guidelines state a commission applies to sales, and the agency relationship belongs to the platform rather than to you, which matters if you later want to move your portfolio.