EOL.WikiEOL.Wiki
← ← Back to all products

Font Awesome

Active
Libraries & SDKsLatest Version: 7.3.1Latest Release: Jul 15, 2026

Font Awesome is the most popular icon toolkit providing scalable vector icons for web projects.

Support summary

Font Awesome currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

No announced EOL date is currently listed.

Supported cycles

3

2 lts

Versions

7

Latest Version

7.3.1

Active Support

3

EOL

4

Lifecycle Timeline

Today
7
7
6
6
5
5
4
4
3
3
2
2
1
1
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
7Jul 22, 2025YesNo7.3.1No
Active
6Feb 7, 2022YesNo6.7.2
Yes
Active
5Feb 5, 2018YesNo5.15.4
Yes
Active
4Oct 23, 2013NoYes4.7.0No
EOL
3Jan 2, 2013NoYes3.2.1No
EOL
2Jun 4, 2012NoYes2.0.0No
EOL
1Mar 3, 2012NoYes1.0.0No
EOL

Data sources

Frequently Asked Questions

Which versions of Font Awesome have reached end of life?
The following Font Awesome versions have reached end of life and no longer receive security updates: 4, 3, 2, 1. It is recommended to upgrade to a supported version.
Is it safe to continue using Font Awesome 4?
Font Awesome 4 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Font Awesome?
The latest version of Font Awesome is 7.3.1, released in the 7 release cycle.
How many versions of Font Awesome are currently supported?
Font Awesome currently has 3 actively supported version(s): 7, 6, 5.
When does Font Awesome 7 reach end of life?
Font Awesome 7 does not have a specific end-of-life date announced yet.
What should I do when Font Awesome reaches end of life?
When a Font Awesome version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.