Generate one personalised PDF certificate for each participant from a single template, then send them in batches of roughly 100 to 200 a day rather than all 500 at once. A single Gmail send to 500 people hits the platform's recipient limit. A free account sending one certificate per email sits exactly at the 500-per-day cap, which leaves no room for test sends or copies. Spreading the work over several days, with a test send to yourself first, is the safe way to do it.
Check your sending limit before you start
The figures differ by source, so start with the most official one. Gmail Help says the "You have reached a limit for sending mail" error appears when one email goes to more than 500 recipients or when more than 500 emails are sent in a day. It says sending resumes within 1 to 24 hours [1]. Gmail Help also suggests creating a Google Group and sending to that group's address to avoid the limit [1].
Secondary guides report higher figures for paid Google Workspace accounts, at 2,000 emails per day. They say the recipient count, not the message count, is what matters [2]. One guide puts Workspace mail merge at 1,500 per day [3], while another says 2,000 per day per user [14]. We could not confirm either figure on Google's own Workspace admin page. Treat them as unresolved and plan for the lower number.
A Google Apps Script run from a Sheet is reported at 50 recipients per email, 100 recipients per day on personal Gmail, and 1,500 recipients per day on Workspace [4]. Reply.io says each email can have up to 100 recipients on any account type [5]. That conflicts with the 500-per-message figure in Gmail Help. Because the sources disagree, the safest design is one certificate per email, sent to one recipient, in small daily batches.
Method 1: Word or Google Sheets merge, one file per person
The usual approach has three parts. You make one file per participant. You upload those files to Google Drive and put each file's link in a spreadsheet column. Then you send the emails with a mail merge that reads the name, address and file link from each row [6].
Word's built-in mail merge is not enough on its own. Microsoft says a mail merge email needs a MAPI-compatible program such as Outlook or Gmail installed. The email column must also have an address for every recipient [7]. Microsoft Q&A states that Word's built-in mail merge does not support file attachments [8]. A PDF-focused guide adds that Word's "Send Email Messages" cannot send each person their own certificate as a PDF [9].
The workaround in Word is Finish & Merge, then Edit Individual Documents. This creates one file per row, which you can export as PDFs [9]. Once you have 500 PDFs, name each file after the participant and attach or link it in your mail merge.
The Google Sheets Mail Merge add-on's marketplace listing says it has no limit on the number of emails it sends. Gmail's account caps still apply to the sending account [10]. The add-on does not get around the daily cap. It keeps the work in one place.
Method 2: Google Slides route with one presentation per row
If your design lives in Google Slides, the Mail Merge add-on's "merge into multiple files" option creates one presentation per spreadsheet row [11]. You can export each one to PDF. The files come quickly, but sending is a separate step, so you still batch the emails under the same Gmail caps.
Portant, a Slides add-on, generates one certificate per spreadsheet row in a single run. It does not send them [12]. You will need a second tool or a manual mail merge for delivery.
Comparison of the main routes
| Route | What it does | What it does not do | Source |
|---|---|---|---|
| Word mail merge plus Edit Individual Documents | Makes one document per row, exportable as PDF | Does not attach a PDF per person when sending | [9] |
| Google Sheets Mail Merge add-on | Sends merged emails from a Sheet, with Drive links | Does not lift the Gmail daily cap | [10] |
| Slides mail merge (multiple files) | Creates one presentation per row | Does not send the certificates | [11] |
| Portant | Generates one certificate per row in one run | Does not send them | [12] |
| Vendor tools such as Certifier | Claims to generate and email certificates in bulk | Treat as vendor marketing; check the sending limits | [13] |
Certifier also says Word's mail merge can produce ready-to-print PDFs for bulk download [13]. That covers the file-making step. You still control the sending.
Batching plan for 500 participants
Assume your sending account is a free Gmail account with a 500-per-day cap, sending one certificate per email. At 200 a day, the job takes three days: 200 + 200 + 100 = 500. At 100 a day, it takes five. Both leave room for a test send and for copies kept in your Sent folder.
One vendor advises batching above 200 recipients [6]. So 200 a day is a sensible ceiling, even on a Workspace account, because the Workspace figures are secondary reports and Google has not confirmed them.
A practical sequence:
- Build one template and test it with five or ten sample rows.
- Generate all 500 PDFs. Name each file with the participant's name and registration ID.
- Send a test merge to your own address, using a single certificate. Check the attachment or link.
- Send batch one of 100 to 200 recipients. Wait for it to finish before starting the next.
- Keep a log of which rows have been sent, so a second run does not email the same person twice.
To re-send to someone who missed the first email, put them in a separate small batch. Do not re-run the whole list. Certificates are usually the last job in a fest, so set the close-out dates in the college fest checklist before you schedule the sends.
Our view
Our view: for 500 people, the sending step is not a single click. Make the PDFs first, check the template with a test merge, and treat the daily cap as the real constraint. Ask the Space's organiser or admin to keep a sent log, so the team can answer questions about who received what.
Where Unifesto fits
If you run the event on Unifesto, certificates come from the Space's own template. Public online verification is part of that Pro feature, so a reader can check a certificate without contacting the club. For how verifiable e-certificates work in general, read our guide to issuing verifiable e-certificates. Certificates are also tied to check-in. If you are planning the gate, how to check in 2,000 people without long queues covers that side. Our notes do not confirm a one-click bulk send to 500 people, so check the current certificate tools on /organisers before you plan around them.
A limitation
The sending limits are the weakest part of this advice. The figures come from Gmail Help and from vendor and secondary guides that disagree with one another. We could not open Google's Workspace admin page to confirm the Workspace numbers. Our research also found no India-specific source on these limits or on the rules for sending certificates, so the figures here are global. Check your own account's current cap before you run the batches.
FAQ
Can I send 500 certificates in one Gmail email?
No. Gmail Help says an email to more than 500 recipients triggers the sending limit error [1]. Send one certificate per email in small daily batches instead.
Why not use the Google Group trick?
Gmail Help suggests creating a Google Group and sending to its address to avoid the limit [1]. That can work for a single announcement. Personal certificates need their own file for each person, so a Group only partly solves the problem.
Can Word send each person their own PDF?
Not directly. A PDF-focused guide says Word's Send Email Messages cannot send each person their own certificate as a PDF [9]. Export one file per row with Edit Individual Documents first, then send the files separately.
How long will the batches take?
At 200 a day, 500 certificates take three days. At 100 a day, they take five, following the batching plan above. Adjust the batch size to match your account's cap.
Sources
- Limits for sending & getting mail - Gmail Help: https://support.google.com/mail/answer/22839?hl=en
- Understanding Gmail's Email Sending Limits [2026]: https://www.gmass.co/blog/understanding-gmails-email-sending-limits/
- Gmail Sending Limits in 2026: How Many Emails Per Day?: https://www.saleshandy.com/blog/gmail-mass-email-sending-limit-per-day/
- Gmail Sending Limits: How Many Emails Can You Send a Day?: https://yamm.com/blog/gmail-sending-limits/
- Gmail Sending Limits Explained: What You Need to Know in 2026: https://reply.io/blog/gmail-sending-limits/
- Mail Merge with Attachments in Gmail: https://qualtir.com/blog/mail-merge-with-attachments-gmail
- Use mail merge in Word to send bulk email messages: https://support.microsoft.com/en-us/word/use-mail-merge-in-word-to-send-bulk-email-messages
- Mail merge with a regular email and to also attach a certificate made on Word - Microsoft Q&A: https://learn.microsoft.com/en-gb/answers/questions/5927033/mail-merge-with-a-regular-email-and-to-also-attach
- How to Mail Merge Certificates to PDF from Excel: https://mailmergic.com/blog/how-to-generate-pdf-certificates-with-pdf-mail-merger
- Mail Merge - Google Workspace Marketplace: https://workspace.google.com/marketplace/app/mail_merge/218858140171
- How to Generate Certificates with Google Forms: https://activitymessenger.com/blog/how-to-generate-certificates-with-google-forms/
- Make Certificates - Easy, Online, Free: https://www.portant.co/make-certificates/
- How to Send Certificates Through Email in Bulk (2026): https://certifier.io/blog/how-to-send-an-email-with-certificates-to-multiple-recipients-3-ways-to-do-it
- Gmail Sending Limits for 2026 + How to Send More!: https://www.trulyinbox.com/blog/gmail-sending-limit-per-day/