I built an open-source certificate generator because I was tired of creating certificates manually

Every college event, hackathon, webinar, or workshop seems to end the same way:

Someone has to generate hundreds of certificates.

Then rename them.

Then email each participant.

It's repetitive, time-consuming, and surprisingly easy to make mistakes.

A while ago, I faced the same problem. What started as a small script to automate certificate generation slowly evolved into a complete project.

Today, it's called MailMyCertificate.

What it does

• Upload your own certificate template
• Import recipients from CSV or Google Sheets
• Generate personalized certificates
• Send them directly through Gmail
• Process data locally whenever possible to keep participant information private

Why I made it open source

I wanted people to see exactly how it works, contribute ideas, and improve it together. Many schools, NGOs, communities, and hackathons don't have large budgets, so keeping it free and open felt like the right choice.

Things I learned while building it

• Building the product is easier than getting people to discover it.
• Good documentation matters almost as much as good code.
• Privacy isn't just a feature—it's something many organizers genuinely care about.
• Small UX improvements save users more time than adding dozens of new features.

I'd love your feedback

If you've ever organized an event or built tools for educators or communities:

• What's the most frustrating part of certificate generation?
• Is there a feature you'd expect that I haven't thought of?
• What would make a tool like this genuinely useful for you?

Project:
🌐 https://mailmycertificate.tech

GitHub:
https://github.com/Akshatthakur22/MailMyCertficate

I'm always open to suggestions, bug reports, and contributions. Thanks for reading!

![ ](https://dev-to-uploads.s3.us-east-2.amazonaws.com/uploads/articles/hp5z6h09ucmnf1exn2sj.png)
![ ](https://dev-to-uploads.s3.us-east-2.amazonaws.com/uploads/articles/ga7agkei84g9nignlgbp.png)