The GitHub Student Developer Pack lasts as long as your student verification stays active, and GitHub re-checks that verification on a roughly two-year cycle rather than expiring the pack on a fixed calendar date. Verification itself, the initial approval step, typically takes about 72 hours after you submit. When your verification lapses, whether from a re-check failing or from graduation, the pack lapses at your next scheduled check rather than instantly, and some individual partner offers (JetBrains among them) run their own separate annual renewal on top of GitHub's cycle.
The duration timeline at a glance
| Stage | Duration or timing |
|---|---|
| Initial verification decision | About 72 hours after you apply |
| Active pack duration | As long as verification stays current, re-checked on a roughly two-year cycle |
| JetBrains license specifically | Renews yearly on its own schedule, separate from GitHub's re-check |
| At graduation | Pack lapses at your next scheduled re-check, not immediately |
| Post-graduation JetBrains discount | 40% off for two years, as a soft landing |
The pack does not have a single hard expiration date the way a signup credit or a fixed-term trial does. It is a status, not a countdown, and the status is tied to your verification remaining current.
How long does GitHub education last
"GitHub education" and "the pack" refer to the same underlying status. As long as you remain a verified student, per GitHub's periodic re-checks, your access to GitHub Pro, the partner offers, and the education status itself continues. There is no separate, shorter expiration for the education designation distinct from the pack overall.
How long does GitHub student verification take
The initial verification decision typically lands within about 72 hours of submitting your application at education.github.com/pack. That is the number for a first-time application. Re-verification, which happens periodically to confirm you are still enrolled, is generally faster in practice since you are usually confirming existing status rather than establishing it from scratch, though GitHub does not publish a separate SLA for re-verification specifically.
If your verification is taking noticeably longer than 72 hours, the most common cause is documentation quality rather than a backlog: an undated student ID, a document without your full name, or a personal email address instead of a school-issued one all commonly cause silent delays or rejections rather than a quick approval. The full breakdown of what causes rejections is in the GitHub Student Pack guide.
What happens when your verification lapses
Two distinct triggers cause a lapse: GitHub's periodic re-check failing (you did not respond, or you are no longer enrolled), or graduation ending your enrollment outright. In either case, the effect is the same and it is not instant: your pack status lapses at your next scheduled re-check rather than the moment your enrollment technically ends. Practically, this means:
- GitHub Pro drops back to GitHub Free once the pack lapses. You keep your account and repositories; you lose the enhanced repo insights and Codespaces allowances tied to Pro.
- The JetBrains license expires on its own separate clock, since JetBrains re-verifies annually independent of GitHub's cycle. Graduates get a 40% discount for two years as a transition, rather than losing IDE access outright.
- Unclaimed timed offers are simply gone. Offers like the DigitalOcean student pack credit or DataCamp's free months do not carry over past the lapse; anything you have not redeemed by the time verification ends is unavailable.
What to do before graduation, given the timing
Because the lapse happens at your next scheduled check rather than instantly on your graduation date, there is often a real window between finishing school and losing pack access. That window is worth using deliberately:
- Redeem any timed offers you have been saving. If you held off on DigitalOcean's credit or DataCamp's trial to use closer to a capstone project, your final term is the point to actually claim them, since they will not survive past your verification lapsing.
- Start migrating anything built on student-only licenses. If your primary IDE license is the free JetBrains student grant, plan the transition to the paid tier or the 40% graduate discount before the free license actually expires, not after.
- Do not assume an exact date. Because the exact re-check timing is not published as a fixed calendar event tied to your graduation date, treat your final semester as the deadline rather than waiting for a lapse notification.
How verification renewal actually works while you are still enrolled
If you are mid-degree rather than graduating, GitHub's periodic re-check simply asks you to reconfirm enrollment, generally with the same school email or documentation process used originally. There is no indication that renewal is harder or slower than initial verification; the main risk is the same documentation issues that cause initial rejections; a school email that has since been deactivated, or a name mismatch introduced by a legal name change, are the kinds of things worth checking before a scheduled re-check catches you off guard.
Why the pack's duration is structured this way
It is worth understanding why GitHub built the pack around a status-based, periodically re-checked model instead of a fixed subscription-style expiration, because it changes how you should plan around it. A fixed expiration date (say, one year from verification) would force every partner offer inside the pack to expire on the same schedule regardless of when a student actually needs them, and it would force GitHub to re-verify every student on the same calendar day, creating a predictable surge of documentation to process. A rolling, periodic re-check tied loosely to typical enrollment lengths avoids both problems: individual partner offers like JetBrains and DigitalOcean can run their own schedules suited to their own business needs, and GitHub's re-verification load spreads out across the calendar rather than clustering.
The practical upshot for a student is that "how long does the pack last" does not have a single clean answer the way "how long does a free trial last" does. The honest answer is: indefinitely, as long as you remain a verified student and respond to GitHub's periodic re-checks, with the individual partner offers inside carrying their own separate timers once redeemed. Treat the pack itself as an ongoing status you maintain rather than a countdown you are racing, and treat each individual timed offer inside it (DigitalOcean's 12-month credit window, DataCamp's 3 months, GitKraken's 6 free months) as the actual clocks worth tracking on a calendar.
The single most important date to actually track
Given all of the above, the one date worth writing down is not a GitHub-issued expiration, since none exists in a fixed form. It is your own expected graduation date, or the date your enrollment status will change for any reason (transferring schools, taking a leave, switching to a non-degree program). Set a reminder for the term before that date to redeem any timed offers you have been saving and to check whether any tool you depend on daily, especially a JetBrains IDE license, needs a paid transition plan lined up before its own separate renewal cycle catches you without access.
Bottom line
The GitHub Student Developer Pack lasts for as long as your verification stays current, re-checked on a roughly two-year cycle rather than a fixed expiration date, with initial verification decisions landing in about 72 hours. Graduation ends the pack at your next scheduled re-check rather than immediately, giving you a real window to redeem timed offers and migrate off student-only licenses like JetBrains before they lapse. For everything inside the pack and the full rejection-avoidance checklist, read the complete GitHub Student Developer Pack guide. Create a free Perkstack account to track this alongside 200 plus other verified student and startup perks.
Related reading: GitHub Student Developer Pack 2026: the full guide, student developer tools in 2026, AI tools for students.
rest of this guide
The rest of this guide picks up at "What to do before graduation, given the timing".
- What to do before graduation, given the timing
- How verification renewal actually works while you are still enrolled
- Why the pack's duration is structured this way