Back to docs
GitHub Student Developer Pack
Free developer tools worth hundreds of dollars for verified students: cloud credits, domains, IDEs, GitHub Copilot Pro, and more. Full process, start to finish.
1. Check eligibility
You qualify if all of these are true
- You are at least 13 years old.
- You are currently enrolled in a degree- or diploma-granting course of study (school, college, university, or a homeschool equivalent).
- You have a verifiable school-issued email address, or documents that prove your current student status (student ID card, enrolment letter, fee receipt with a current date).
- You have a personal GitHub account (free tier is fine).
2. Prepare your proof
Indian schools rarely issue student emails. Documents work too.
- Best: a school email address (e.g.
you@school.edu.in) added and verified in your GitHub email settings. - Otherwise: photograph your school ID card or a dated enrolment document. The name on the document must match your GitHub profile name.
- GitHub asks you to capture the document with your device camera during the application, so keep the physical document handy.
3. Apply
Takes about 10 minutes
- Sign in to GitHub, then go to education.github.com/pack and click Sign up for Student Developer Pack.
- Select your school from the list (add it manually if missing).
- Fill in how you plan to use GitHub, then upload/capture your proof of enrolment.
- Enable two-factor authentication and complete your GitHub profile (real name and bio) before submitting. Incomplete profiles are a common rejection reason.
- Submit and wait. Most applications process within a few days; peak periods can take longer.
4. After approval
What you actually get
- GitHub Pro features on your personal account while you remain a student.
- GitHub Copilot Pro at no cost.
- Partner offers: free domains (Namecheap, Name.com), cloud credits (DigitalOcean, Azure for Students, Heroku), JetBrains IDEs, and dozens more. Each redeemed from the pack page.
- Benefits expire when you can no longer verify student status. GitHub re-verifies periodically, so keep your proof current.
Rejected? Most common causes: mismatched names, undated documents, missing two-factor authentication. Fix the issue and reapply. No penalty.
Sources
Official documentation this guide is based on