---
schema_version: "1"
id: 58b8a7cd1a37ac209ca24314ebb62ec28a6b2e48fbacd366bda3a01a2981690f
title: Managing Package Version Settings for Visualforce Pages and Components
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/salesforce-pages-developers-guide/guides/pages/packaging/pages-packaging-manage-version.md
canonical_url: https://developer.salesforce.com/docs/platform/salesforce-pages-developers-guide/guide/pages-packaging-manage-version.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 869f0eeb51ea29c40fc14f1f33f9d603e80296c625a8ef5c046a018f956f7b36
products:
  - Visualforce Developer Guide
  - Platform Developer Content
---

# Managing Package Version Settings for Visualforce Pages and Components

If Visualforce markup references installed managed packages, the version settings for each managed package referenced by the Visualforce markup are saved to aid backwards-compatibility. This ensures that as the components in managed packages evolve in subsequent package versions, a page is still bound to versions with specific, known behavior.

A package version is a number that identifies the set of components uploaded in a package. The version number has the format _majorNumber.minorNumber.patchNumber_ (for example, 2.1.3). The major and minor numbers increase to a chosen value during every major release. The _patchNumber_ is generated and updated only for a patch release. Publishers can use package versions to evolve the elements in their managed packages gracefully by releasing subsequent package versions without breaking existing customer integrations using the package.

To configure the package version settings for a Visualforce page or custom component:

1.  Edit a Visualforce page or component and click **Version Settings**.
2.  Select a `Version` for each managed package referenced by the Visualforce page or component. This version of the managed package will continue to be used by the page or component if later versions of the managed package are installed, unless you manually update the version setting. To add an installed managed package to the settings list, select a package from the list of available packages. The list is only displayed if you have an installed managed package that isn’t already associated with the page or component.
3.  Click **Save**.

Note the following when working with package version settings:

-   If you save a Visualforce page or custom component that references a managed package without specifying a version of the managed package, the page or component is associated with the latest installed version of the managed package by default.
-   You can’t **Remove** a Visualforce page or component’s version setting for a managed package if the package is referenced by the page or component. Use **Show Dependencies** to find where the managed package is referenced.
-   Package subscribers can use package versions to reference deleted components. Visualforce pages within a package always use their own package's latest API version. They cannot access deleted components.

**See Also**  


-   [How Visualforce is Versioned](https://developer.salesforce.com/docs/platform/salesforce-pages-developers-guide/intro/pages-intro-versioning.md)
-   [Managing Version Settings for Custom Components](https://developer.salesforce.com/docs/platform/salesforce-pages-developers-guide/comp-cust/pages-comp-cust-versioning-manage.md)
-   [What are Custom Components?](https://developer.salesforce.com/docs/platform/salesforce-pages-developers-guide/comp-cust/pages-comp-cust-def.md)