Visualforce Components
Visualforce Components is a Setup page that lists all custom Visualforce components in the org.
Definition
Visualforce Components is a Setup page that lists all custom Visualforce components in the org. Visualforce components are reusable UI building blocks that can be embedded in Visualforce pages, similar to how Lightning Web Components work in the Lightning framework. They encapsulate markup and controller logic for reuse.
In plain English
“Here's a simple way to think about it: Visualforce Components are the reusable building blocks of Visualforce pages - the Visualforce-era equivalent of Lightning Web Components. The Setup page lists them all; the catalog is migration units.”
Worked example
A developer at CloudSync reviews the Visualforce Components page and finds a reusable component called "AddressForm" that renders a standardized address input form with validation. Instead of rebuilding address collection logic for a new Visualforce page, she includes the existing component with a single tag, maintaining consistency across all pages that collect addresses.
Why Visualforce Components are the reusable building blocks of Visualforce pages
A Visualforce Component is the Visualforce-era equivalent of a Lightning Web Component - a reusable UI building block with its own markup and controller logic that can be embedded in Visualforce pages. The Setup page lists all custom Visualforce components in the org, with their API versions and dependencies. For teams maintaining a Visualforce codebase, this is the inventory of reusable parts.
The reason it's worth knowing about even on orgs migrating to Lightning is that Visualforce Components often become migration units. Identifying which custom components are still in active use, which can be retired, and which should be rewritten as Lightning Web Components is the kind of catalog work that turns a vague Visualforce-migration goal into a concrete project plan. Audit the page during migration planning, treat each component as a discrete decision, and the migration becomes scopable rather than overwhelming.
How organizations use Visualforce Components
Audit identified custom Visualforce Components in active use; migration to LWC scoped from the catalog.
Compliance review verified each Visualforce Component's purpose; deprecated components retired.
Trust & references
Straight from the source - Salesforce's reference material on Visualforce Components.
- Standard Component ReferenceSalesforce Developers
Test your knowledge
Q1. What skill set is typically needed to work with Visualforce Components?
Q2. What is a Governor Limit in the context of Visualforce Components?
Q3. Where would a developer typically work with Visualforce Components?
Discussion
Loading discussion…