Angular supports most recent browsers. This includes the following specific versions:
(4.1, 4.2, 4.3)
Angular is built on the latest standards of the web platform. Targeting such a wide range of browsers is challenging because they do not support all features of modern browsers.
You compensate by loading polyfill scripts ("polyfills") on the host web page (
A particular browser may require at least one polyfill to run any Angular application. You may need additional polyfills for specific features.
The tables below will help you determine which polyfills to load, depending on the browsers you target and the features you use.
The suggested polyfills are the ones we know will run full Angular applications. You may need additional polyfills to support features not covered by this list. Note that polyfills cannot magically transform an old, slow browser into a modern, fast one.
These are the polyfills required to run an Angular application on each supported browser:
|Browsers (desktop & mobile)||Polyfills required|
|Chrome, Firefox, Edge, Safari 9+||None|
|Safari 7 & 8, IE10 & 11, Android 4.1+|
Optional browser features to polyfill
Some features of Angular may require additional polyfills.
For example, the animations library relies on the standard web animation API, which is only available in Chrome and Firefox today. You'll need a polyfill to use animations in other browsers.
Here are the features which may require additional polyfills:
|Feature||Polyfill||Browsers (desktop & mobile)|
|Animations||All but Chrome and Firefox|
Not supported in IE9
|Date, currency, decimal and percent pipes||All but Chrome, Firefox, Edge, IE11 and Safari 10|
|NgClass on SVG elements||IE10, IE11|
|Http when sending and receiving binary data||IE 9|
Below are the polyfills which are used to test the framework itself. They are a good starting point for an application.
|Intl||MIT / Unicode licence||13.5KB|
* Figures are for minified and gzipped code, computed with the closure compiler