Your Salesforce version is the seasonal platform release your org is currently running, such as Summer '26. Salesforce ships three major releases a year and upgrades orgs automatically, so the fastest way to determine your Salesforce version is to refresh any page and watch for the release logo, or look up your instance on Salesforce Trust. This guide shows you how to check your release and API version, explains how Salesforce versioning works, and covers what to do before each upgrade.
How to Determine What Version of Salesforce You Have
Here are the quickest ways to determine what version of Salesforce you have.
- Refresh any page. As the page reloads, Salesforce briefly displays the current release logo, for example an Astro graphic with the release year. This is the fastest visual check.
- Check Salesforce Trust. Go to the Salesforce Trust status site, enter your instance (the next section shows where to find it), and read the Current Major Release and maintenance schedule for your org.
- Check your API version. Open the services/data URL for your org (https://[YourMyDomain].my.salesforce.com/services/data/) in a browser. The highest number in the list is your current API version, which maps directly to the release.
Each method answers a slightly different question, so the sections below break them down.
Why Knowing Your Salesforce Version Matters
Knowing your Salesforce version is not just trivia. It affects security, since each release ships fixes and new controls; compatibility, since integrations and managed packages target specific API versions; feature availability, since new capabilities arrive by release; and release planning, since you need to know your upgrade window to test in time. For admins and DevOps teams, version awareness is the baseline for safe, predictable deployments.
How to Find Your Salesforce Version in Setup
Setup does not show the seasonal release as a single field, but it gives you the two details you need to look it up.
- Go to Setup. Click the gear icon, then Setup.
- Open Company Information. In the Quick Find box, type Company Information and select it.
- Note your Edition and Instance. The Organization Edition field shows your edition, such as Enterprise or Unlimited. The Instance field shows your backend instance, for example NA123 or a Hyperforce instance.
- Look up the release on Trust. Enter that instance on the Salesforce Trust status site to see your Current Major Release.
A note on older guidance: instructions that say the System Overview page displays your version are inaccurate. System Overview shows usage and limits, not your release.
Understanding Salesforce Release Versions
Salesforce names releases by season and year, not by a single decimal number. There are three each year: Spring, Summer, and Winter, followed by the year, for example Winter '26 or Summer '26. The release name is the label for a bundle of features and API changes, and it is separate from your edition. You may still see older content referencing numeric versions like v45.1; that format is outdated. Today the release is seasonal, while the API version is a whole number, for example 67.0.
How to Use Salesforce Release Notes
Salesforce Release Notes are the authoritative source for what changes in each release: new features, retirements, and required Release Updates. Review them before your upgrade window so nothing catches your team off guard. Filter the notes by the clouds and features your org uses, and pair them with Release Updates in Setup, which lists updates that have enforcement deadlines you need to test and activate.
Understanding Salesforce Release Cycles
Salesforce upgrades every org automatically, three times a year, during scheduled maintenance windows. Exact dates vary by instance, which is why Trust is the source of truth for your timing. Sandboxes matter here too: during each release, preview sandboxes are upgraded weeks before production, so you can test against the new release early, while non-preview sandboxes stay on the current release until production upgrades. Note that a release name does not always match the calendar year; Winter '26, for instance, began rolling out in late 2025.
How to Check Your Salesforce API Version
Your API version controls how integrations and code communicate with Salesforce, and it maps one-to-one to the release. To check your Salesforce API version, open the services/data URL for your org and read the highest version in the list, or in Setup open any Apex class and check Version Settings, which lists the available API versions. The API version matters for integrations, middleware, and developer tooling, because calling an old version can mean missing fields or deprecated behavior. It is related to, but not the same as, the platform release.
Salesforce Version vs. API Version: What's the Difference?
These two get confused constantly. The platform release is the seasonal version of Salesforce your org runs; the API version is the numeric interface version your integrations and code target. They move together, since each release increments the API version by one, but you reference them in different situations.
What to Do Before Your Next Salesforce Release
A little preparation each season prevents surprises. Before your upgrade window, work through a short checklist.
- Review the Release Notes for features and retirements that affect your org.
- Check Release Updates in Setup and test anything with a pending enforcement deadline.
- Test customizations and automations in a preview sandbox.
- Validate integrations against the new API version.
- Back up your metadata and data so you can recover if something regresses.
- Plan and stage your deployments so changes ship in a controlled way.
A structured release management process makes this repeatable instead of a scramble. This is where a dedicated release management and backup platform helps teams stay ready release after release.
Keep Your Salesforce Org Ready for Every Release
Determining your Salesforce version is quick once you know where to look: refresh for the logo, confirm on Trust, and check your API version through the services/data endpoint. The bigger win is building a habit, checking your version and release notes each season, testing changes in a preview sandbox, backing up before upgrades, and deploying through a repeatable process.
Flosum supports that discipline with Salesforce release management, backup and recovery, and deployment automation purpose-built for Salesforce, so your team can move from each release to the next with less risk. Request a demo to see how it fits your release process.
Frequently Asked Questions (FAQ)
Thank you for subscribing




