Canva does not hand contributors an FTP endpoint. Uploads move through the Elements Hub in your browser, and the metadata travels with them as a CSV placed inside the folder you drag in. That single structural difference changes how you stage, name and batch files compared with every FTP agency in your rotation.
If you already deliver to Adobe Stock or Shutterstock over FTP, the instinct is to go looking for a host, a username and a password. There is nothing to find. Canva belongs to the group of marketplaces that accept a web upload with a CSV manifest rather than a file transfer, and planning around that from the start saves a lot of wasted staging work.
Why there is no FTP endpoint to point at
Canva's catalogue is built for people designing inside an editor, not for buyers browsing a stock library, and its contributor pipeline reflects that. Creators publish two kinds of content: elements, which Canva describes as design assets like photos, graphics, illustrations, vector art, icons and custom stickers, and templates, which are customisable layouts for presentations, social graphics, video and print. Both go through the Creators pipeline rather than a contributor FTP tree.
Payment follows the same logic. Canva says creators earn royalties based on their content's performance, and that every time your designs are used you can earn royalties. That is usage rather than per-download, and it matters for upload planning: a coherent, well-described collection gets reached for repeatedly, while a scattered dump gets browsed and abandoned. The shape of the Creator program itself is worth reading before you plan your first batch.
The collection is the unit of upload, not the file
Canva's own framing is that uploading elements as a collection lets you submit same-style elements together, with the metadata making them more searchable. In practice you build a folder on your own machine, put the CSV inside it alongside the assets, and drag the whole folder into the Elements Hub page. The folder is the transaction.
This is the inverse of an FTP run, where files land one by one and metadata is either embedded in each file or delivered as a separate manifest the agency reconciles later. Here, if the CSV is missing from the folder, the assets still arrive but without the metadata that makes them findable, and Canva accepts only content that has metadata. The field-by-field requirements are worth having open while you build the sheet.
Building the CSV Canva will actually read
The spreadsheet itself is ordinary. What matters is column discipline. File name has to match the element's file name exactly, extension included. Title needs its main words capitalised, with articles, conjunctions and prepositions left lowercase. Keywords need at least five, separated by a comma and a space. Artist and Description are both optional but preferred, and Locale carries the regional default for the elements you are submitting.
One practical note comes straight from Canva's own instructions: it suggests avoiding Windows devices for the CSV upload where possible. If Windows is your only machine, export the file and confirm it opens cleanly with the delimiter and encoding intact before you drag the folder in. A CSV that looks fine in a spreadsheet app can still arrive with its columns collapsed into one.
Canva collection metadata CSV
The column set Canva's contributor documentation asks for: File name matching the asset exactly including its extension, a title-cased Title, at least five Keywords separated by a comma and a space, plus optional Artist, Locale and Description fields.
The six steps inside Elements Hub
Once the folder is right, the submission itself is short. The whole sequence lives in the browser, and nothing about it rewards doing it one file at a time.
Submitting a Canva element collection
The submission sequence Canva documents: build a folder holding the assets and the metadata CSV, open Elements Hub from the homepage side menu, drag the uncompressed folder in, mark the elements Pro or Free, confirm ownership, then click Submit collection and verify the metadata applied.
File naming is where multi-agency pipelines break
Canva's submission guidance asks for a unique name on every file, or submission inside a folder, so that new uploads do not overwrite earlier ones. On a single-agency workflow that reads as mild housekeeping. On a pipeline that also feeds FTP agencies it becomes a hard constraint, because the file name is simultaneously the join key your Canva CSV depends on and the sort key everything downstream relies on.
The fix is to settle on one naming scheme before the first upload rather than after the first collision, and to apply it to the originals so every destination inherits it. A naming convention that survives multi-agency delivery costs nothing to adopt early and is painful to retrofit across a library.
Compressed folders are rejected before review
Zipping a collection feels like the tidy thing to do, and it is the one habit most likely to waste a submission. Canva does not accept compressed files, so the archive has to be expanded before you drag anything in. It is worth separating that kind of mechanical failure from the content and format problems that get caught later: Canva's actual rejection reasons sit downstream of this step, and a packaging mistake never gets that far.
Pro or Free, ownership, and releases
Two decisions are made at submission rather than beforehand. You mark the elements as Pro or Free content, and you confirm you own what you are sending. Releases are not demanded at that moment, but Canva expects you to be able to produce them on request, which in practice means storing them with the originals from the day of the shoot. Attaching releases correctly across agencies is easier when the paperwork never leaves the asset folder.
What Canva does not publish, and how to plan around it
Canva's public contributor documentation is deliberately quiet on several numbers people would like to have. There is a published keyword floor but no stated ceiling. There are no published character limits for titles or descriptions. There is no stated file count or size cap for a collection, and no published review timing. Third-party guides fill those gaps with confident figures, and those figures are not sourced from Canva.
The workable posture is to treat the unpublished limits as unknown rather than generous. Keep collections to a size you can verify by eye after submission, keep keyword sets relevant instead of maximal, and resist the urge to pad toward a number nobody has confirmed. Padding is the behaviour moderation teams look for, and a ceiling you invented is a poor reason to risk it.
Fitting Canva into a multi-agency run
If Canva is one destination among several, the awkwardness is not the upload but the shape of the metadata. FTP agencies generally read what is embedded in the file. Canva reads a CSV sitting next to it, in its own column order, with its own capitalisation rule for titles. Writing metadata twice is how inconsistencies creep in, so the better pattern is to hold one canonical record per asset and map those fields outward to each agency's requirements rather than retyping per destination.
It also helps to notice that Canva is not the only destination with a manifest format of its own. Comparing its sheet against a Shutterstock CSV template makes the pattern obvious: same facts, different column names, different separators, different expectations about case. Once you see them side by side, the case for generating each sheet from one source instead of maintaining several by hand gets hard to argue with.
A short pass before you hit submit
Expand any archive. Confirm every file name in the CSV matches its asset exactly, extension included. Check that each row carries at least five comma-and-space separated keywords and a title with its main words capitalised. Make sure the CSV is inside the folder, not beside it. Decide Pro or Free before you start rather than mid-flow. Then submit, open one element, and read its Add Metadata section back to confirm the sheet landed.
Rastock.ai was built for exactly this shape of problem: one metadata pass per asset, then delivery out to the agencies in your rotation in whatever form each one expects, with policy-aware keywords, banned and mandatory term handling, rollback on a bad batch, and per-agency status you can actually read. It does not take a revenue share, does not claim ownership of your files, and lets you export IPTC or CSV freely. You can see how the workflow fits together or go straight to the plans — there is a 14-day free trial and it does not ask for a card.
Frequently asked questions
Does Canva accept FTP uploads from contributors?
No. Canva's contributor path is the Elements Hub in the browser, where you drag in a collection folder containing your assets and a metadata CSV. There is no published FTP or SFTP endpoint for element submissions, so a delivery pipeline built only around file transfer needs a separate step for Canva.
How do I attach metadata to a Canva collection?
Export your metadata spreadsheet as a CSV and place it inside the collection folder before uploading. Canva reads it on submission and applies each row to the matching asset by file name. You can also skip the CSV and type metadata manually in the Add Metadata section, and selecting several elements applies the same details to all of them.
Can I upload a zipped folder to Canva?
No. Compressed files are not accepted, so unzip the folder before you submit. Canva also asks that each file carry a unique name, or that files be submitted inside a folder, so that a new upload does not overwrite something you sent earlier.
How many keywords does a Canva element need?
At least five, separated by a comma and a space. Canva publishes the floor but not a ceiling, so there is no verified maximum to aim for. Keep the set relevant to what the asset actually shows rather than padding it toward a number you cannot confirm.
Why can I not see Elements Hub in my Canva account?
Usually because the active team is not your Creator brand. Click the account icon, open the Switch team section and select the Creator brand. If it is not listed there, you are probably signed in to a different account than the one your contributor application was approved on.
Do I need model releases before uploading to Canva?
Not at the moment of upload. Canva asks you to confirm ownership when you submit a collection, and releases are not required at that point. You must be able to produce them on request, though, so collect and store them alongside the originals rather than chasing them afterwards.