Last checked: 17 November 2026, against angular.dev/reference/releases. This page tracks Angular end of life dates for every version and is updated with every Angular major release and every LTS expiry.
As of today, Angular 20 reaches end of life on 28 November 2026. Angular 21 is in long-term support until June 2027, and Angular 22 - the current active version - is supported until June 2028. Angular versions 2 through 19 are no longer supported by the Angular team. If your app runs Angular 19 or older, it is already past end of life; if it runs Angular 20, you have until the end of this month.
Below: the exact dates for every supported version, the dates for the versions that have already expired, what losing support means in practice, and the three realistic options when you are behind.
Which Angular versions are supported right now?
Version
Status
Released
Active support ends
LTS ends
Angular 22
Active
3 June 2026
June 2027
June 2028
Angular 21
LTS
19 November 2025
3 June 2026
June 2027
Angular 20
LTS
28 May 2025
19 November 2025
28 November 2026
Source: Angular versioning and releases, 17 November 2026. Where angular.dev gives a month rather than a day, the month is shown.
Everything older than Angular 20 is unsupported. The official page says it in one line: Angular versions v2 to v19 are no longer supported.
When did earlier Angular versions reach end of life?
Version
Released
Active support ended
LTS ended (end of life)
Angular 19
19 November 2024
28 May 2025
19 May 2026
Angular 18
22 May 2024
19 November 2024
21 November 2025
Angular 17
8 November 2023
8 May 2024
15 May 2025
Angular 16
3 May 2023
8 November 2023
8 November 2024
Angular 15
16 November 2022
3 May 2023
18 May 2024
Dates for versions 15 to 19 are from endoflife.date/angular, checked 17 November 2026; the Angular team removes expired versions from its own table, so the independent tracker is the reference once a version drops off. Angular 2 through 14 expired earlier under the same 18-month rule that applied before version 22.
How does Angular's support policy work in 2026?
The policy changed with Angular 22. Until then, Angular shipped a new major every six months and supported each one for 18 months: six months of active support, then 12 months of LTS. From version 22 onward, a major release ships every 12 months and each major is supported for 24 months - 12 months active, then 12 months LTS.
What the two stages mean:
Active: regular minor releases, features, bug fixes and patches.
LTS (long-term support): only critical fixes and security patches. A fix is considered for an LTS version if it resolves a newly identified security vulnerability or a regression caused by a third-party change such as a new browser version. Nothing else.
The next scheduled milestones on angular.dev are v22.3 around November 2026, v22.4 around January 2027, v22.5 around March 2027 and v23.0 around June 2027 - which is also when Angular 21 leaves LTS.
One rule that matters for teams behind on updates: ng update works one major version at a time, and only towards a version that is still supported. If you are on Angular 16 and want 22, that is six sequential updates, and the intermediate targets are themselves unsupported - the tooling still works, but you are passing through versions nobody patches.
What does Angular end of life mean in practice?
Nothing breaks on the day. Your app keeps compiling and running. What changes is everything around it:
No security patches. Vulnerabilities found after the LTS date are fixed in supported versions only. CVE-2025-66412, a stored XSS flaw in Angular's template compiler published in December 2025, was patched in 19.2.17, 20.3.15 and 21.0.2; the advisory lists 18.2.14 and everything below it as affected with no patched version. That is the pattern: once a version is out of support, every new CVE is yours to carry.
Audits and procurement. Enterprise security questionnaires, SOC 2 evidence requests and vendor-risk reviews ask for the framework version and whether it is under vendor support. An unsupported Angular version is a finding, and increasingly a blocker for closing enterprise deals.
Dependency drift. Libraries drop old Angular peer dependencies quickly: component kits, charting libraries, auth SDKs, even the TypeScript version your build tolerates. The longer you wait, the more packages you have to pin to old releases, and the more of those old releases carry their own unpatched issues.
Hiring and velocity. Engineers expect signals, standalone components and the current build system. A codebase on Angular 14 with NgModules everywhere is harder to staff and slower to change, and every feature estimate quietly includes the cost of working around the old version.
What should you do if your Angular version is already out of support?
Three options, in the order most teams should consider them.
1. Update to a supported version. For anything from Angular 15 up, this is usually the right call: sequential ng update runs, breaking changes handled per major, the Angular update guide as the checklist. Expect the jumps that remove deprecated APIs (standalone by default, new control flow, the build system switch) to take the most time. Our Angular migration service article walks through how an update project is scoped.
2. Buy extended support. Third-party vendors sell security patches for Angular versions past their official date - HeroDevs sells this under its Never-Ending Support line, currently for Angular 4 through 19. It is a legitimate option when the update cannot happen before an audit or a contract deadline, and a poor one as a permanent state: you are paying to stand still, and the gap to the current version keeps growing.
3. Migrate, when the version is very old or the app is due for more than an update. If the app is on Angular 2 to 9, built around patterns that no longer exist, or the product itself needs rework, a sequential update can cost as much as a planned migration. The destination is Angular or React, depending on the product - current Angular if the team and codebase are Angular-native, React if the product roadmap, hiring plan or the rest of your stack point that way. We cover the React path in Angular to React and the React-side service on React migration services; for the Angular path, Angular development services is the entry point.
How do you plan an Angular update before the LTS date?
If you are on Angular 20 with days to go, or on 21 with months, this is the sequence that keeps the update boring:
Map the path. Current version to target version, one major at a time. Note which majors carry the breaking changes that touch your code (the update guide lists them per jump).
Check the compatibility matrix. Angular, TypeScript, Node, RxJS and zone.js versions have to line up; the version compatibility table is the source. A mismatch here is the most common reason an update stalls on day one.
Inventory third-party libraries. Every dependency that declares an Angular peer dependency needs a version that supports your target. The ones with no maintained release are your real risk - plan a replacement or a fork before you start.
Run the update on a branch with the full test suite. Unit and e2e. If coverage is thin, add smoke tests on the critical flows first; an update without tests is a guess.
Timebox per major. Most jumps are hours; a few are days. Knowing which is which before you start is the difference between an update and an open-ended project.
If the team has no capacity for this alongside feature work, that is exactly the engagement we take on through Angular consulting.
Is Angular 21 LTS a safe place to sit?
Until June 2027, yes - it receives security patches. But Angular 21 is the last version released under the old six-month cycle, and Angular 22 is the first under the new 12-month cadence with 24 months of support. If you are updating from 20 anyway, going to 22 buys a full extra year of support for roughly the same effort as stopping at 21. Stop at 21 only if a specific dependency is not ready for 22.
What about AngularJS (1.x)?
AngularJS is a different framework with a different history: Google's long-term support for it ended on 31 December 2021, and the official AngularJS site states that support officially ended as of January 2022. Nothing on this page applies to it. If you are still running AngularJS, the choice is extended commercial support, an upgrade to current Angular, or a rewrite to React - we compare the three in AngularJS end of life, and the framework comparison is in Angular vs AngularJS. The migration path itself is covered in AngularJS to Angular migration.
Where The Frontend Company fits
We are a frontend engineering company that works with Angular and React, and updating Angular applications that fell behind the support window is one of our entry engagements. The shape is always the same: we look at the version, the dependency matrix and the test coverage, give you an estimate, and then a fixed price for the update - the work is not billed by the hour. If the honest answer is that the app needs a migration rather than an update, we say so and scope that instead, on Angular or React depending on your product. Start on the Angular consulting page or book a call.
For the wider question of whether Angular is still a sound long-term choice, see Is Angular dead? - the short version is no, and the yearly release cycle introduced with version 22 is part of why.
Angular 20 leaves long-term support on 28 November 2026. After that date it receives no security patches from the Angular team. Its active support already ended on 19 November 2025, when Angular 21 shipped.
No. Angular 19 reached end of life on 19 May 2026 and is listed on angular.dev among the versions that are no longer supported, together with every version from 2 to 19.
Active support brings regular minor releases, new features and all bug fixes. LTS brings only critical fixes and security patches - nothing else is backported. Since Angular 22, each phase lasts 12 months; before that, active support lasted six months.
Versions 22 and later are supported for 24 months from release: 12 months active, 12 months LTS. Versions up to 21 were supported for 18 months: six months active, 12 months LTS. Angular 21 is the last version on the old schedule and leaves LTS in June 2027.
ng update moves one major at a time, and only to versions that are still supported. From Angular 16 to 22 that is six sequential updates. Each jump can be short if the app has tests and few deprecated APIs; the jumps that remove deprecations take longer.
The app keeps running, but new vulnerabilities go unpatched, libraries stop releasing compatible versions, security audits flag the framework, and the eventual update grows more expensive with every major you skip. Extended-support vendors can buy time for a deadline, not a strategy.
Alex Vasylenko is the founder of The Frontend Company, DBC and several other successful startups. A dynamic tech entrepreneur, he began his career as a frontend developer at Deloitte and Scandinavia's largest banking company. In 2023, Alex was honored as one of 'Top 10 Emerging Entrepreneurs' by USA Today.
Alex Vasylenko is the founder of The Frontend Company, DBC and several other successful startups. A dynamic tech entrepreneur, he began his career as a frontend developer at Deloitte and Scandinavia's largest banking company. In 2023, Alex was honored as one of 'Top 10 Emerging Entrepreneurs' by USA Today.
Pavlo runs operations and delivery at The Frontend Company and builds its internal AI systems - agent workflows, automation, and the engineering side of software compliance.