Leaving a stock workflow tool is two separate problems that people tend to treat as one. Getting your metadata out is straightforward when the tool wrote it into your files and awkward when it only ever lived in the vendor's database. Getting your content out of a managed distributor is slower, governed by its terms rather than by a button, and in some respects not fully possible at all.
The real question is where the metadata physically lives
Before comparing tools, it is worth being precise about what you would be trying to take with you. There are usually four things: the titles, descriptions and keywords themselves; the mapping of which file went to which agency under which name; the release paperwork attached to people and property; and the credentials and FTP endpoints you configured. Only the first of those is normally described as an export feature. The other three are quietly the ones that hurt.
The deciding factor for the first is whether the tool embeds metadata into the file or keeps it in a remote record. A tool that writes IPTC and XMP into your JPEGs and MOVs has effectively already given you the export: uninstall it tomorrow and the keywords are still in the originals, readable by Bridge, Lightroom, exiftool or the next tool you try. A tool that generates results into a web account has given you nothing until you use its export, which means the export's existence and its field coverage are the entirety of your portability.
Desktop tools: the files are already yours
Xpiks is the clearest case for portability, and deliberately so. It documents CSV export with a scheme you define yourself: each column gets a name you choose and a value such as Filename, Description or Keywords, you can add a column that is intentionally left empty so you can fill it in later, and since version 1.6 you can set a fixed value that repeats on every row. The vendor frames this as useful for uploading video to microstock, for sharing metadata with other people, and explicitly for backups. That last word is the one that matters here. CSV is the only export format its documentation names, which is a limit, but a CSV you control the shape of is a genuinely portable artefact.
StockSubmitter sits differently. Its own interface reference describes a program that browses folders on your computer and reads embedded metadata with a priority order of EXIF, then IPTC, then XMP, with buffers and templates for copying metadata between images inside the program. It is strong at what it is for, which is driving submissions to a lot of agencies from one desktop window. What that reference does not document is a file-based import or export of your catalogue, so if portability matters to you, treat it as an open question to settle with the vendor rather than an assumption. Being desktop software is itself a kind of insurance: the install and the files are on your machine.
Cloud generators: export is a feature, not a right
PhotoTag.ai generates in the cloud and offers three ways out, which its own site summarises as exporting with metadata, a Lightroom Classic plug-in, or an API. For anyone whose catalogue already lives in Lightroom, the plug-in route is the strongest of the three, because the keywords land in a library you already own rather than in a vendor list you have to move later. The API matters for a different reason: a tool you can call programmatically is a tool you can also systematically read back out, which is not true of a web interface alone.
The general rule for anything cloud-based is to run the export once, on real files, during the trial, and look at what comes back. Not whether a button exists, but whether the output carries every field you rely on, in a form something else can read.
Where your metadata lives, and what you can take with you
Compares five routes on where metadata is stored, what export the vendor documents, what cannot be taken out, and the mechanics of leaving. Xpiks documents a user-defined CSV; PhotoTag.ai documents export with metadata plus a Lightroom plug-in and API; StockSubmitter's interface reference documents no file-based export; Wirestock's terms close an account within 120 days and state that Wirestock owns the metadata it created.
Managed distributors: leaving is a process with a clock on it
A distributor is a different kind of commitment from a desktop utility, and Wirestock is the useful example because it publishes the mechanics in its terms of use rather than leaving them to support tickets. You keep your copyright and the licence you grant is non-exclusive, which are both genuine strengths and not universal in this part of the market. The 85/15 split on downloads is stated plainly. So is the exit.
You request termination by emailing support with Termination in the subject line, and the account closes within 120 days. Wirestock then has 90 days to pull content off marketplaces for up to 100 items, with another 30 days for each additional 100, and its own terms note that some marketplaces may take up to a year. Work out what that means for a portfolio of a few thousand files and you get a removal window measured in quarters, not days. Twelve consecutive months of inactivity can also terminate an account from their side.
The part most contributors have not considered is that removal is not retraction. The terms state that licences granted before termination survive, that marketplace licences and sublicences for content that is later removed remain in effect in perpetuity, and that licences already held by end customers cannot be retrieved because the content is no longer in anyone's reach. Leaving stops new licensing. It does not unwind the licensing that already happened, and no distributor can honestly promise otherwise.
The clause that catches people: who owns the metadata
Here is the line worth reading twice. Wirestock's terms state that you keep the copyright in your content, and separately that Wirestock owns the metadata created by it or by others including its contractors and partners. Those two sentences are compatible, and together they mean something specific: the photograph is yours, the keyword set written for it on the platform is not. If you spent two years building a portfolio there and then decide to self-distribute, you are taking the files and leaving the descriptions.
The same terms also say you have no rights in what they call Developed Technology, meaning the models or datasets built using your content, and that content submitted on or after 20 January 2026 is not licensed to content marketplaces at all but joins the Dataset Deals programme automatically. Whether that is a good trade is a separate question and depends on what you shoot. The point for this article is narrower: it is a structural change to what the platform is for, and it is the kind of change that makes people want an exit route they have not checked.
When to use which
If you expect to change your mind
Prefer anything that writes into the file. Xpiks is the strongest documented case for a user-controlled export, and it costs you the work: you build and maintain the CSV scheme, and you drive the submissions yourself. If you would rather not do that but still want the metadata in your originals, look for IPTC and XMP embedding as a named feature rather than an implied one, and test it on a real file before you commit a season's work to it.
If you want someone else to do the submitting
A managed distributor genuinely removes work, and for a contributor who does not want to run FTP, keywording and agency-by-agency rules, that trade can be worth 15%. Go in knowing the exit terms rather than discovering them later: the notice period, the removal timeline, who owns the generated metadata, and whether your content feeds model training. The commercial side of the same decision, including which tools take a cut and which charge a flat fee, is compared in stock tools without a revenue share.
If you are evaluating something right now
Do the exit test during the trial, while you have nothing to lose. Run a batch of twenty real files through the tool, export, and open the result somewhere else. Then look at the credentials question, because the agency logins and FTP endpoints you hand over are the other half of the lock-in and are covered separately in the safest way to give a tool access to your stock accounts. A tool that passes both tests is one you can leave, which is the only reliable reason to feel comfortable staying.
The exit test, before and during a trial
A checklist for testing portability before you commit: confirm whether metadata is embedded or remote, run a real export and open it elsewhere, read the ownership and termination clauses, and record the agency mapping and credentials you would otherwise lose.
What a clean exit actually looks like
A clean exit is one where the only thing you lose is the software. The metadata is in the originals or in a CSV you can read. Your own spreadsheet, however ugly, records which file went where under which name. The release paperwork is in your folders. The agency credentials are yours and were never shared in a form you cannot revoke. None of that requires a particular vendor to behave well; it requires you to have set it up before you needed it.
The version worth avoiding is the one where the keywords are in a web account you have stopped paying for, the agency mapping only ever existed in the tool's database, and the distributor's removal clock has four months left to run. That situation is not usually the result of a bad vendor. It is the result of nobody asking the portability questions while the trial was still free.
Where Rastock AI sits in this
Rastock AI is a subscription tool, so the honest version of its exit story is this: generation stops when you stop paying, and that is a real dependency. What it deliberately does not do is hold the output. Metadata is embedded into your files as IPTC and XMP, CSV and XML export are available rather than gated, delivery runs over FTP and SFTP to 10+ agencies on credentials that stay yours, and no ownership or revenue-share claim is made on anything you put through it. Where it is a poor fit is equally clear: agencies that publish no FTP endpoint cannot be automated by anyone, and a contributor who wants another party to handle submission and curation entirely wants a distributor, not this. The pipeline is described here, and the 14-day trial needs no card, which is long enough to run the export test above before deciding anything.
Frequently asked questions
Can I export my metadata from a stock workflow tool?
It depends entirely on where the tool put it. Desktop tools that write IPTC and XMP into your files leave nothing behind when you uninstall them, because the metadata is in the originals. Cloud tools hold results in their own database until you export, so the export feature is the whole of your portability. Check that it exists and that it covers every field before you build a routine around the tool.
Does Wirestock own my metadata?
Wirestock's terms of use state that Wirestock owns the metadata created by it or by its contractors and partners, while you keep the copyright in your content itself. In practice that means the keywords and descriptions generated on the platform are not yours to carry to another distributor, even though the images and clips remain yours.
How long does it take to leave Wirestock?
Wirestock's terms say you request termination by emailing support with Termination in the subject line, and the account closes within 120 days. Wirestock then has 90 days to remove content from marketplaces for up to 100 items, with 30 more days for each additional 100, and notes that some marketplaces may take up to a year. Licences granted before termination survive.
What happens to images already licensed through a distributor when I leave?
They stay licensed. Wirestock's terms are explicit that licences granted before termination survive, that marketplace licences and sublicences for content later removed remain in effect in perpetuity, and that licences already held by end customers cannot be retrieved. Leaving a distributor stops new licensing; it does not unwind the licensing that already happened.
Does Xpiks export to anything other than CSV?
Xpiks documents CSV as its export format. What makes it usable is that you define the export scheme yourself: each column gets a name you choose and a value such as Filename, Description or Keywords, you can include deliberately empty columns to fill in later, and since version 1.6 you can set a fixed value that repeats for every row. The vendor also names backup and sharing as valid uses, not just upload.
What should I check before committing to any stock tool?
Whether metadata is written into your files or only stored remotely, whether there is a documented export and which fields it covers, who owns the generated metadata, whether leaving involves a notice period or a removal timeline, and whether your content can be used to train models. Those five answers determine how expensive it is to change your mind later.