Choose a hosted Kit when appropriate
The official Kit guide describes creating a Kit, selecting its icons and copying its embed code into the HTML head. The guide states that the older Font Awesome CDN supports version 5 and below; a search for a generic CDN link should therefore not be treated as instructions for every newer release.
Choose packages for a build workflow
Font Awesome documents packages for npm, yarn and pnpm. It distinguishes Kit packages, individual SVG icon packages and all-inclusive packages. The Free package includes Free assets; Pro package access has its own requirements. Match the package to the icons actually needed rather than installing the largest collection by default.
Keep technology and version explicit
Record whether the project uses Web Fonts or SVG-based rendering. Kit settings can specify the version and available rendering choices. For naming and version background, use the Font Awesome versions guide rather than combining snippets that assume different releases.
Make the integration maintainable
Keep the chosen delivery method in the project notes, along with the required icon styles. A designer’s icon name is only part of the handoff: the page must also load the matching resources. Keep package access credentials out of public documentation when a private package workflow is used.
Your questions, answered.
Is one old CDN link suitable for every release?
No. The official Kit guide says the older CDN supports version 5 and below.
Must I install every Font Awesome icon?
No. Official documentation describes Kit subsets and individual icon packages as alternatives to all-inclusive packages.
Sources & background
Sources supporting this page’s explanations. Practical examples are our editorial suggestions.