How to bulk send certificates from a Canva design

The short answer

Canva is usually the right place to design the certificate and the wrong place to deliver it. Keep the design, import it into Verifycate once, add the recipient name and a unique QR code as editable fields, then send the whole list from a CSV. Every recipient gets their own tracked page, and you keep one list to correct.

Most certificate problems are not design problems. The design is finished, approved, and sitting in Canva. What is missing is everything after Export: a different name on every copy, a delivery record, a way to fix a typo without resending a file, and a page an employer can check.

This guide compares the realistic ways to send a Canva certificate, explains where each one breaks, and then walks through the route we built: import the finished Canva design, add the fields that change, and issue from a recipient list.

Canva is genuinely good at this

It is worth saying plainly: Canva is a genuinely good design tool, and we are not pretending otherwise.

• The template library is enormous. A student team can find a certificate that looks professional in minutes, without a designer.
• Brand kits keep events consistent. Fonts, colours, and logos stay in one place across a fest, a course, or a whole institution.
• The editor is learnable. A volunteer can be handed a design and trusted not to break it.
• Collaboration works. Comments, shared folders, and approvals fit the way an organising team actually works.
• Bulk Create is real design automation. It fills a design from a spreadsheet, which is exactly the right feature for a design tool to have.
• Export quality is good. PNG and PDF output is print-ready when the design is set up properly.
• The AI features are useful for first drafts. They shorten the blank-canvas problem.

None of that is the problem. The problem starts after the design is approved and the recipient list arrives.

The Sunday-night problem

A familiar sequence:

1. The design is approved on Friday.
2. The registration list is final on Sunday night: 300 names and 300 email addresses.
3. Someone opens the design, changes the name, exports a PDF, renames the file, and repeats. Then repeats again.
4. The files are attached to 300 emails, or uploaded to a folder and announced in a group chat.
5. Forty addresses bounce. Twelve people say their name is spelled wrong. Twenty say they never received anything.
6. The team re-exports the corrected files and sends another round, and the certificate links people already shared stop matching the new file.

The design was never the hard part. The hard part is that a certificate is a personal record with a delivery obligation, and a design tool is not built to hold either.

Canva's Bulk Create limits were read from Canva's help centre on 28 October 2026. Canva changes plans and limits, so check the current help page before quoting a number.

What "sending" actually requires

Before comparing tools, it helps to name the jobs. A certificate send is not one action; it is seven.

1. Personalise. Put the right name, award, date, and details on each copy.
2. Deliver. Get a unique certificate to a unique person, from a sender they recognise.
3. Handle bounces. Find the addresses that failed and fix them.
4. Handle corrections. Fix a name without invalidating the link the recipient already has.
5. Handle missing people. Collect details from people who attended but are not on the list.
6. Verify. Give a third party a way to check that the certificate is real.
7. Keep a record. Know who was issued what, when, and which version.

Canva does job one well. The other six are the reason people start looking for a sending tool.

The realistic options, compared

There is no single best route. The right one depends on batch size, whether verification matters, and how much post-send work you are willing to do.

Competitor features and pricing below were read on 28 October 2026. They change; treat this as a map of the categories, not a permanent scorecard.

Option 1: Export each file and email it

The default. It is fine for a handful of certificates, and it requires no new tool.

• Best for: under about 10 certificates, or a one-off award where verification does not matter.
• Strengths: total control, no setup, no subscription.
• Breaks at: the second correction. Every resend creates another file, and the recipient may end up with two versions and no way to tell which is current.

Option 2: Canva Bulk Create, then download and send

Canva Bulk Create is the closest Canva gets to a certificate workflow. You connect a spreadsheet to a design, generate a page per row, and download the pages.

• Best for: a few dozen to 300 certificates, with a paid Canva plan and a patient organiser.
• Strengths: the personalisation is genuinely automatic, and the design stays in the tool the team already knows.
• Breaks at: delivery. Bulk Create produces a multi-page design, not 300 emails. Someone still downloads, separates, names, and sends the files. Above 300 rows, the upload must be split and the exports merged by hand. There is no delivery record, no correction link, and no verification page.

Option 3: Mail merge from Gmail, Outlook, or Sheets

A mail-merge add-on can send personalised emails from a spreadsheet, often with the certificate attached or linked.

• Best for: teams already living in Google Workspace or Microsoft 365, with a simple design and a modest list.
• Strengths: familiar tools; the email can be personalised as well as the file.
• Breaks at: attachment limits, deliverability, and the absence of a record. A bounced attachment is hard to trace, a corrected certificate means resending a file, and the recipient still has no verification page. Many add-ons also cap daily sends, which matters the night before results are announced.

Option 4: A free browser-based generator

Tools such as MailMyCertificate and Certly take a PNG or JPG template and a CSV, generate personalised PDFs in the browser, and help send them through Gmail. Both position themselves as privacy-first and free.

• Best for: a budget of zero, a single batch, and an organiser who is comfortable with a technical workflow.
• Strengths: no cost, no account for many of them, and the file never has to leave the machine in the local-first variants.
• Breaks at: everything after the file. There is no public verification page, no correction flow, no recipient record, and no delivery analytics. If the certificate needs to be checked by an employer six months later, a PDF in a downloads folder is not a record.

Option 5: A certificate platform

This is the category Verifycate belongs to. Platforms such as Certifier, Certopus, CertPie, Creadefy, Activity Messenger, and Verifycate combine a template, a recipient list, delivery, and some form of verification.

The difference that matters for this guide is how each one treats a design you already made in Canva.

Most platforms start with their own template library and expect the design to live inside their editor. Your Canva file becomes a PNG or PDF upload, if it is supported at all, and every artwork change means exporting and uploading again. Others accept an image background and add fields on top, but the Canva step stays manual: export, upload, align, repeat. A few offer a Canva connection, though it is often a side door rather than the main path.

Verifycate treats the Canva design as a first-class starting point. Connect Canva, pick the finished design, and it arrives as the certificate background. The name, award, and QR code are added once. The recipient list, delivery, corrections, verification page, badges, forms, API, and analytics are part of the same product, so there is no export-upload-realign loop when the artwork changes and no second tool for the send.

That difference matters most when the design already exists.

If you are starting from scratch, any platform with a strong template library can work. If the design is finished in Canva and the event is next week, the shortest path is the one that starts with the file you already have — and that's Verifycate.

The comparison, in one table

Why we added a Canva import

The request kept coming back in the same shape: "Our design is already in Canva. We do not want to rebuild it."

For a while, the answer was to export a PNG and upload it as the certificate background. That worked, but it added a manual step and a place to make a mistake. So we built the connection: authorise Canva once, pick the design from your account, and import it directly as the background.

The import is deliberately one-way. Canva remains the source of the artwork. Verifycate becomes the place where the artwork is personalised, issued, corrected, and verified.

Two limits are worth knowing before you start:

• The design is flattened. Text inside the imported image is not editable. Anything that changes per recipient has to be added as an Attribute over the background.
• The first page is imported. A multi-page Canva design brings in page one. Use one design per certificate page.

Neither limit is hidden in the product, and this guide is written around them.

The workflow, step by step

Step 1: Design the Canva file so the import works

The import turns your design into a background. That keeps the artwork exactly as you made it, and it is why the variable fields must sit above it.

Before you leave Canva, check five things:

• Leave a blank area for the name. Do not put a placeholder name in the artwork.
• Reserve a corner for the QR code. A clear square of roughly 2.5 cm (1 inch) at print size, usually bottom-right.
• Do not bake in the award, date, or cohort if those change between groups. Add them as Attributes instead.
• Keep each certificate to one page. A second page should be its own design.
• Test a long name. A 40-character name should still fit the space you left.

Step 2: Connect Canva and import the design

Open the certificate in Verifycate, choose Design, and start from Use Your Canva Design.

1. Connect Canva. A Canva authorisation window opens; approve it once.
2. Search for the design by name, or browse the designs in the connected account.
3. Pick the finished certificate.
4. Verifycate exports the design and imports it as the certificate background.

If the artwork changes later, import the new version and republish. Recipients who were already issued keep the version they received.

Step 3: Add the recipient name and the QR code

With the background in place, add the fields that change:

• Recipient name, as an Attribute such as {{name}}.
• Award, track, team, or course, if the event has more than one group.
• Issue date, if the certificate shows one.
• The verification QR code, added from the design editor.

A QR added inside Canva is a static link: every copy points to the same place. The QR added in Verifycate is unique to the recipient and resolves to their certificate page, so the code on a printed copy still proves who it belongs to.

Step 4: Import the recipient list

Export the list from wherever it already lives: a registration form, a Google Sheet, an LMS, or the event platform. Import it as CSV or Excel, or paste the rows directly.

At minimum, the file needs a name, an email address, and any Attributes you added to the design. Map the columns once. Verifycate normalises email addresses and flags duplicates and malformed rows before anything is issued.

If some people are missing from the list entirely, do not guess their details. On Pro, share the Issue Request Form after the batch and choose Review Before Issuing, so holding the link is not enough to receive a certificate.

Step 5: Review and send

When the list and the design are ready, publish the certificate. The confirmation states how many certificates will be issued and how many credits the batch will use. Read it against your list before confirming.

Each recipient receives an email with a link to their own certificate page, not a PDF attachment. The page carries the download, the QR code, and the verification details, and it stays current if the certificate is later corrected.

Write the email around the outcome, not the file:

Your [Event] certificate is ready

[Name], here is your [Event] certificate

Include what the certificate recognises, the link, how to fix a name, and a date after which corrections close. On Pro, send from your own verified domain, provider, or SMTP so the email comes from the event rather than a stranger.

Step 6: Handle bounces, corrections, and late recipients

Bounces. Open the delivery events and look at the addresses that failed. Fix the address on the recipient record rather than dropping the person.

Name corrections. On Pro, enable the Correction Form and give recipients a deadline, usually seven days. An approved correction updates the same certificate and public page, keeps the existing link working, and does not use another issuance credit.

Missing people. On Pro, share the Issue Request Form for anyone who attended but is not on the list. Review submissions before issuing so the link alone does not qualify someone.

Public certificate pages are excluded from search indexes, so a recipient's name does not become a search result. The page is still reachable by anyone with the link or QR, which is what verification requires.

What it costs

• 300 free credits on signup, no card required. A first batch of up to 300 certificates costs nothing.
• One credit per certificate issued. Importing the design and the list does not spend credits.
• Corrections do not spend another credit.
• Credits never expire. Pro is time-limited; credits are not.
• Pro is a workspace plan, from ₹499/month with 100 credits, ₹999/quarter with 300, or ₹2,999/year with 1,200. USD equivalents are shown at checkout; billing is in INR.
• Top-ups are available in packs when a batch is larger than the free allowance.

You do not need Canva Bulk Create for this workflow, and you do not need to rebuild the design in another editor. If your Canva plan does not offer the connect or export option, export the design as a PNG and use the manual artwork upload instead.

Where Verifycate is not the right choice

An honest guide has to include this section.

• Under about 10 certificates, with no verification need. Exporting from Canva and emailing the files is simpler and cheaper.
• You need to keep editing the design in Canva. The import is a flattened background. If the artwork changes constantly and must remain editable, design changes belong in Canva.
• You want a design tool, not an issuing layer. We are not replacing Canva's editor, template library, or brand kit.
• You need an employer-recognised badge network. That is a different category, closer to Credly. We are built for event and cohort certificates, not employer badge networks.
• You require SOC 2, ISO 27001, or a formal procurement process. We do not hold those attestations and say so publicly.
• You need a native integration for an LMS other than Canvas or WordPress. CSV, the API, webhooks, and Zapier cover the gap, but they are not a native connector.

Extra benefits beyond bulk sending

Bulk sending is the reason people arrive. These are the parts that keep the certificate operation from turning into another spreadsheet.

Recipient operations

• Issue Request Form (Pro). A public form for people who attended but are missing from the list. Applicants confirm their email with a one-time code; you choose automatic issue or review first.
• Unlock Form (Pro). Hold a certificate until the recipient submits feedback, a testimonial, a project link, or a file. Useful when the event needs a response before release.
• CSV, Excel, paste, API, webhooks, Zapier, and MCP. Bring the list from wherever it already lives, or automate the next cohort. CSV, Excel, and paste work on every plan; the API and MCP are Pro.
• One row per recipient, with Attributes. Award, track, team, role, and course can all be fields on the same design.

Delivery and corrections

• Email delivery from a shared sender or your own domain (Pro). The email comes from the event, not a stranger.
• Delivery events. See issued, delivered, bounced, opened, clicked, and page views per certificate.
• Correction Form (Pro). The recipient fixes a name from their certificate page. The same certificate and link update; no extra credit is used.
• Reissue controls. A design change is a version change, not a silent edit to someone's existing certificate.

Verification and trust

• A public page for every certificate. The recipient, issuer, title, issue date, and status live on one page.
• A unique QR code. A printed or downloaded copy still resolves to the recipient's page.
• Signed Open Badge 3.0 data. The credential is machine-readable, not just a picture.
• Add to LinkedIn. Recipients add the certificate with a link back to the verification page.
• Expiry and revocation. Set an expiry where it makes sense, or revoke a credential; the public page reports the status.
• Blockchain anchoring (Pro, optional). An independent timestamp for teams that need one. Verification does not depend on it.

Design and credential formats

• Digital badges as well as certificate pages. A credential can carry a square badge mark, up to ten page and badge designs, or both.
• Multi-page credentials. A certificate page and a transcript or results page can sit under one public ID.
• Sponsor slots (Pro). Sponsor logos, links, and captions on the public page, without forcing every mark onto the certificate itself.
• AI design drafts and reusable Templates. Useful when there is no Canva file, or when the next cohort needs the same design with a new date.

Administration

• Workspaces and roles. Keep a fest, a department, and a training programme separate without separate accounts.
• Custom domain and logo removal (Pro). The recipient sees the event's brand, not ours.
• SSO, SCIM, and audit logs (Pro). For institutions that need identity and access controls.
• Credits that never expire. Buy for one event, use the remainder at the next one.
• India-first pricing. INR billing and per-certificate costs that a student organiser can understand.

Common questions

Can I send certificates directly from Canva?

Not to a list, in one go. Canva can personalise a design from a spreadsheet with Bulk Create, and it can email a single design, but it does not deliver a different certificate to every recipient with tracking. You still download the files and send them one by one, or move the design into a tool that handles delivery.

Can I keep my Canva design and still send in bulk?

Yes. Connect Canva from the certificate design step, pick the finished design, and import it as the certificate background. The artwork stays as you designed it. You then add the recipient name and a unique QR code as editable fields over the background, import the recipient list, and send.

Does the imported Canva design stay editable?

No. The import is a flattened image background, not a live Canva document. Text inside the image cannot be edited in Verifycate. Anything that changes per recipient, such as the name, award, or date, should be added as an Attribute over the background. Canva remains the source of the artwork.

How many certificates can I send at once?

Verifycate gives you 300 free credits on signup, with no card, so a first event of up to 300 recipients costs nothing. Larger batches use top-up credits, which do not expire. Canva's 300-row Bulk Create limit does not apply here, because you are importing the design, not a Bulk Create export.

What if my Canva design has more than one page?

The Canva import currently brings in the first page of the design. Use one design per certificate page, and import the next page as its own certificate if you need a second page such as a transcript.

Do I need Canva Pro to do this?

You do not need Canva Bulk Create, which is the feature limited to paid Canva plans. You need a finished design in Canva that you are able to export or connect. Check your Canva plan if the connect or export option is unavailable, and use the PNG upload fallback if it is.

Can recipients verify a certificate that started in Canva?

Yes. Every issued certificate gets a public page and a unique QR code. The QR resolves to that recipient's page, where the issuer, recipient, certificate title, and status are shown. The same record carries signed Open Badge 3.0 data and an Add to LinkedIn action.

What happens if a name is wrong after sending?

Enable the Correction Form. The recipient requests the change from their certificate page, confirms their email with a one-time code, and you approve or apply it. The same certificate and public page update, the existing link keeps working, and no additional issuance credit is used. The Correction Form is a Pro feature.

Is Verifycate a Canva alternative?

No, and it is not trying to be. Canva is the design tool; Verifycate is the issuing layer after the design is finished. You keep designing in Canva. Verifycate adds the recipient record, bulk delivery, corrections, and public verification that a design tool does not provide.

What if I only have 10 or 20 certificates to send?

If the batch is small and nobody needs to verify the certificate later, exporting from Canva and emailing the files yourself is a reasonable choice. Verifycate becomes worth the extra step when people need a stable link, when names are likely to be corrected, or when the same design will be reused for the next cohort.

The honest summary

Canva should keep the design. It is the best tool for that job, and nothing in this guide argues otherwise.

The question is what happens after the design is approved. If the batch is tiny and nobody will ever need to check the certificate, export and email is fine. If the batch is large, if names will change, or if a recipient needs a link that still works next year, a design tool cannot carry that obligation.

That is the gap Verifycate fills: import the Canva design once, add the fields that change, send from a list, and keep a record that survives the send. The design stays in Canva. The certificate becomes something a recipient can keep and a third party can check.