---
schema_version: "1"
id: f914b8a8a5d81d4f1f28dea7f453a2f11c4c7746ea2a7f271ad2d69f81bf4be4
title: Get the Latest LWC Changes with LWC API Version 68.0
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/264-0-0/rn_lwc_versioning.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_lwc_versioning.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a9f0427d93271a3ecf8bd3e305d05e156e6b7d3ca9ad6f101a4d912fab4b12f7
description: Update the API version for your components to use new features and improvements. Versioning your Lightning web components ensures that your existing components aren’t affected when Salesforce ships new features, bug fixes, and performance improvements that change existing behavior. Versioning also helps Salesforce deprecate legacy features.
products:
  - Cross Cloud
release: "264"
---
# Get the Latest LWC Changes with LWC API Version 68.0

Update the API version for your components to use new features and improvements. Versioning your Lightning web components ensures that your existing components aren’t affected when Salesforce ships new features, bug fixes, and performance improvements that change existing behavior. Versioning also helps Salesforce deprecate legacy features.

**Where:** This change applies to custom Lightning web components in Lightning Experience, Experience Builder sites, and all versions of the Salesforce mobile app.

**How:** You can change a component's API version in its .js-meta.xml file.

```markup
<?xml version="1.0" encoding="UTF-8"?>
      <LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata">
      <apiVersion>68.0</apiVersion>
      </LightningComponentBundle>
```

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-release-notes-salesforce_release_notes-264-0-0-production-enus/550ba85b-db1a-4608-9cd4-9a65ec96e1fa/images/icon_important.png)

Important We recommend that you upgrade your component API version one version at a time. For example, from 58.0, upgrade from 58.0 to 59.0, fix any errors or warnings you encounter, and then repeat until you get to the latest API version.

When a component’s LWC API version is set to 59.0 or later, it uses that value for its LWC framework version. Components that specify LWC API version 58.0 and earlier continue to work based on LWC framework behavior in Summer ’23 (API 58.0). When you set a component to use an earlier API version, you don’t get new features, bug fixes, and enhancements that are available only with later LWC API versions.

LWC API version 68.0 has no version-specific changes. That makes this release a good one to update your existing components to the current API version.

#### See Also

- [_Lightning Web Components Developer Guide_: API Versioning](https://developer.salesforce.com/docs/platform/lwc/guide/get-started-api-versioning.html)