How to find your Salesforce release version in Setup

Finding your Salesforce release version through Setup

Ever been caught off guard by a new button appearing, or a flow suddenly behaving differently? You probably need to check your Salesforce release version. I've seen teams spend hours debugging a "bug" that turned out to be a new feature from a weekend update. Annoying, but easy to sort out once you know where to look.

Start in Setup. There's no big "Winter '25" banner waiting for you, which is what most people expect to find. What you want is your instance ID:

1. Go to Setup and type "Company Information" in the Quick Find box.
2. Look for the Instance field. You'll see something like NA45, EU17, or AP24.
3. Copy that code. It's what you need to work out the actual release name.

Why doesn't Salesforce print the name right there? Because updates roll out in waves, and different instances get the new version at different times. Once you have the instance code, you can pin down your Salesforce release version with 100% certainty.

Checking the Salesforce release version via Salesforce Trust

So what do you do with that instance code? Take it to the Salesforce Trust site, which is where status updates and maintenance schedules live. I'm on that site at least once a week, making sure my clients aren't about to hit a maintenance window during a big deployment.

Click "Status" and paste your instance code into the search bar. It shows you which version is currently live on that hardware, along with the upcoming schedule. If you want to know what's coming next, I wrote up my notes on the Spring '26 release.

One thing that trips people up: don't just check your production org. Sandboxes often get updated weeks before production. If you're testing new code, always verify the version in both environments first.

The developer way: using CLI and Apex

If you spend half your day in VS Code like I do, clicking through the UI for a version number is a waste. You can pull the instance information from the command line instead, which is much faster when you're juggling multiple scratch orgs or sandboxes.

Run sf org display - target-org myOrgAlias (or the older sfdx version if you haven't switched yet) and look for the "Instance URL". If it says something like https://na123.my.salesforce.com, your instance is NA123.

If you're already in the Developer Console, this snippet in the Anonymous Window gets you the same answer:

String host = URL.getSalesforceBaseUrl().getHost();
System.debug('Your host is: ' + host);

That prints your full URL to the debug logs. Grab the instance part and head back to the Trust site. Handy when you're deep in a coding session and don't want to break stride for a Salesforce release version check.

UI clues and release updates

Sometimes you don't need to leave the org at all. In Salesforce Classic (no judgment here, some of us still love the speed) the footer often shows the current release. Lightning hides it better, but you can always search for "Release Updates" in Setup.

That section is one of the most overlooked in the platform. Along with the version, it tells you which security and logic changes are about to become mandatory. I've seen projects saved by an admin who checked this page and spotted a critical update that was about to break their custom integrations.

What about sandboxes?

Sandboxes are a different beast. Depending on whether yours sits on a "preview" instance or a "non-preview" instance, you might be running a completely different Salesforce release version than production. That's intentional. It gives you a few weeks to play with new features before they go live. If you're not sure which sandbox you should be testing in, this guide on Salesforce sandbox types covers how the schedules differ.

Key takeaways

• Find your instance code in Company Information in Setup (e.g., NA144).
• The Trust site is the only way to see the specific schedule for your hardware.
• sf org display gets you instance details without clicking through menus.
• Preview sandboxes get the Salesforce release version earlier than others.
• The Release Updates menu in Setup tells you what's coming.

Grab your instance code from Setup, then check the Trust site. That's the most reliable method I've found in ten years on the platform. Whether you're a developer trying to use a new Apex class or an admin planning your next training session, knowing where your org stands saves a lot of frustration. Try it next time something "weird" happens in your org. It's usually just a new release making itself at home.