How to Issue Webinar Certificates with a QR Code

Save time (and precious mental energy) by automating webinar certificate issuance with a simple QR code added to your final slide.

Attendees scan it during the last few minutes and fill in a short Certifier Form. A configured Certifier automation uses that data to issue the certificate, then emails it to each participant.

The entire process from scanning to certificate delivery stays in Certifier, without a separate form app, attendee list export, or connector. It works the same on Zoom, Teams, Webex, or any other webinar platform because it doesn’t depend on the platform's data.

The QR code you add at the end of your webinar presentation is a certificate request, which is different from the verification QR printed on a certificate you've already issued. And despite what some may think, scanning it isn't the ultimate proof of webinar attendance.

A QR code on your webinar's final slide opens a Certifier Form, then the Issue Credential action turns each response into a certificate email.

You choose whether attendees get their certificate right after they submit or whether each request waits as a draft for review.

A final-slide scan is a certificate request, not webinar attendance proof, so you must match the route to what the certificate claims.

Show the QR during the closing Q&A, paste the link in the chat, and deactivate the form before the replay goes out.

The slide QR requests a certificate, whereas the QR printed on the certificate verifies it.

What Happens After Webinar Attendees Scan the QR Code

Any tool can put a QR code on a slide. What makes a difference is how many handoffs sit between the scan and a certificate arriving in the attendee's inbox.

Certifier Forms is a native tool that lets you collect submission data through forms with a direct link and a QR code you can drop onto your closing slide. The forms you create live on your issuer portal and include a GDPR consent checkbox by default.

Attendees don't need a Certifier account to access the form or view their certificate. An Automation built from the "Issue a credential via Certifier when a new form response is received in Certifier Forms" template runs the Issue Credential action, which maps the submitted name and email to your webinar's Credential Template.

Two settings decide what happens next. With Issue Credential and Send Credential actions both set to True, attendees get their certificate by email after they submit. With both set to False, each response becomes a draft, so nothing is emailed until you review it.

That's a shorter path than the one many webinar teams run after every session: export the attendee list from the webinar platform, clean it in a spreadsheet, or point a QR at Google Forms, collect responses in a linked Google Sheet, and connect that sheet to a certificate tool directly or through Zapier.

Each handoff is another mapping to maintain and another place to check when an attendee comes back to ask where their certificate is.

Fewer tools isn't automatically better, though. If your webinar platform, registration tool, or LMS already holds the data that decides who qualifies, keep it in the chain.

What the Native Webinar Certificate Generator Workflow Replaces

You still build the form, create the Automation, map fields, and choose whether to issue, send, or save drafts. That setup now happens in one place, plus you can reuse it for every session in a webinar series.

An external stack still earns its place when you need a scored post-webinar quiz with a pass/fail rule or a form that also feeds your CRM. In that case, see how to generate certificates from Google Forms.

A QR Code Submission Is Not Webinar Attendance Proof

Showing the QR code only at the end of the webinar reduces access for attendees who dropped off after ten minutes.

But a code on screen can be photographed, posted in a team chat, or scanned from the recording a week later. A form submission tells you someone entered a name and email when the form was open, while revealing nothing about who watched the webinar or for how long.

Webinar attendance evidence sits on a spectrum, from weakest to strongest:

Example: A 45-minute webinar can trigger two certificate types. The closing slide shows a Form QR for the last five minutes, during Q&A.

Participation certificate. Issue Credential and Send Credential are both set to True. Attendees who submit the form get their certificate by email. The team deactivates the form once the Q&A ends.

Controlled CE credit. Both settings are False, so every submission becomes a draft. After the webinar, the team compares drafts against the Zoom attendance report and issues only the drafts that meet the duration rule.

Choose the Right Webinar Certificate Route

Pick the route based on where your webinar's eligibility evidence lives. For in-person or hybrid events run on Eventbrite, check-in data can play the same role. Certifier's native Eventbrite integration can issue a certificate when an attendee checks in.

Use a QR Code Request When Submission Is Sufficient. Pick this route when the certificate acknowledges participation or when your series runs on more than one platform, and you want one flow for all of them.

Use Zoom Attendance Data When the Platform Record Should Trigger Issuance. If Zoom's record should decide who qualifies, automate Zoom attendance certificates with the Webinar Ended trigger instead of a self-submitted form. You can set a minimum attendance threshold, in minutes or as a percentage of the session, so a brief join doesn't qualify.

Review a Roster When a Human Checkpoint Matters. For credit-bearing webinars, hold form submissions as drafts or skip the form and issue from a reviewed attendee export.

How to Run a QR Scan Certificate Flow for Your Next Webinar

This section follows the webinar timeline. For the full form and Automation walkthrough, see how to let recipients request their own certificate. For exact step-by-step screens, see how to set up and share a Certifier Form QR code.

Before the Webinar

Prepare the webinar's Credential Template. Add the session’s title and date on the webinar certificate template.

Create the Form and connect the Automation. Start from the Credential request template and ask only for full name and email. In the Automation, leave the issue date blank so it's set when the credential is generated, then save and activate. Each plan includes a set number of forms, so many teams reuse one form across a series. If you do, add a required session Dropdown and map it to a custom attribute on the template.

Test it signed out. Scan the QR code from your phone and submit with an internal email. Check that the credential shows up in All credentials, the name renders correctly, and the email doesn't land in spam.

Add the QR code and a short link to your final slide. Make the code large enough to scan from a laptop screen.

During the Closing Minutes

Show the slide during Q&A segment of the session. Attendees need a minute or two to scan while you're still on screen.

Paste the link in the webinar chat. Attendees watching on a phone can't scan their own screen.

Say what happens next. For example, you could say: "Scan to request your certificate. Type your name exactly as it should appear. It'll arrive from [sender] within [timeframe]."

After the Session

Close the request window before the replay goes out. Deactivate the form when your policy says the window ends or decide whether replay viewers qualify. Existing responses stay on the form's Results tab.

Keep the certificate link out of the post-webinar follow-up email, unless registrants who didn't attend should be able to request one too.

Create and Send Digital Credentials

Start issuing certificates and badges in minutes.

Get started. It’s free!

Plan for What Goes Wrong After a Live Webinar

Most problems show up after the webinar ends. Settings can reduce them, but they can't prevent all of them.

Pro Tip: Put one support contact on the final slide and in the certificate email, so recipient requests and questions reach one person.

How to Tell the Two QR Codes Apart: Form Submission vs Certificate Verification

There are two QR codes in this story, and each one does a different job:

Request QR (before issuance) - Lives on your webinar's final slide and opens the Certifier Form. Works only while the form is active.

Verification QR (after issuance) - Printed on the issued webinar certificate and opens the credential's verification page, or a custom URL you choose. You can add a verification QR code to an issued certificate in the Design Builder.

Put simply, the request QR gets you a certificate while the verification QR proves an existing one is genuine.

Match Your Webinar Certificate Workflow to Your Attendance Rules

Start from what the certificate claims. If a submission is enough evidence, let the final-slide QR issue and send. If a platform record or a person should decide, use Zoom data, drafts, or a reviewed roster.

Want to try it before your next webinar? Create a Certifier Form, connect it to your webinar's Credential Template, and test it with your own email. It takes one form, one Automation, and a test scan.

Try Certifier Forms for free or see how built-in forms fit into webinar certificates.