Salesforce Release Dates and Schedule: Winter '27 and Spring '27

Salesforce Winter '27 release dates

Salesforce's official countdown lists the 3 Winter '27 production release days. The exact maintenance window depends on your instance. Salesforce Help also lists 2-day sandbox upgrade ranges. The table keeps those ranges instead of assigning every sandbox the same day.

Sources: Salesforce Winter '27 countdown and Salesforce sandbox preview instructions.

The sandbox refresh must finish before the cutoff. Starting a refresh on the cutoff date does not guarantee completion. Salesforce Help warns that a late request can produce a non-preview sandbox. Check the release type before testing or refreshing.

The countdown's heading says August 27 before 5 p.m. Pacific time. The detailed Help instructions specify a 6 p.m. cutoff that day. This calendar keeps the common date as an all-day planning marker. Use the detailed sandbox instructions for operational decisions, and allow time for the copy to complete.

Time zones can change the displayed day. For example, Trust lists the USA320 Winter '27 start as October 3 at 05:00 UTC. That is October 2 at 22:00 Pacific daylight time.

This example explains the difference without assuming every instance uses that time. See USA320 on Salesforce Trust.

Salesforce Spring '27 release date

Official Salesforce Trust records show Spring '27 preview and production windows in January and February 2027. The following rows identify a specific instance as evidence for each date. They are not a complete instance schedule.

ForceFolks labels these entries Scheduled because they are future planning windows. The underlying Trust records currently use Confirmed. The ICS feed uses TENTATIVE for these 4 Spring planning markers. Check Trust again before scheduling work because Salesforce can change maintenance windows.

The dates in this table are UTC calendar days from the cited records. We do not convert them into a universal local release date. The source record includes the exact start and end times for its named instance. Your org can use another instance and another time.

Separate security deadline: Salesforce's release notes set February 20, 2027 for retirement of the OAuth 2.0 username-password flow for Connected Apps. This is a release-update enforcement date, not another production wave. The cited note does not specify a time zone.

Review affected integrations before that date. Source: Salesforce release updates.

Text values for this chart. Source: ForceFolks reviewed dataset.

Release	Milestone	Dates	Time basis	Status
Winter '27	Release notes published	August 19, 2026	Published calendar date	confirmed
Winter '27	Sandbox refresh cutoff date	August 27, 2026	Pacific planning day	confirmed
Winter '27	Preview sandbox upgrades	August 28 to 29, 2026	Published calendar dates	confirmed
Winter '27	Production wave 1 planning day	September 4, 2026	Pacific planning day	confirmed
Winter '27	Production wave 2 planning day	October 2, 2026	Pacific planning day	confirmed
Winter '27	Production wave 3 planning day	October 9, 2026	Pacific planning day	confirmed
Winter '27	Non-preview sandbox upgrades	October 9 to 10, 2026	Published calendar dates	confirmed
Spring '27	Preview sandbox example	January 9, 2027	UTC planning day	scheduled
Spring '27	Production wave 1 example	January 16, 2027	UTC planning day	scheduled
Spring '27	Production wave 2 example	February 6, 2027	UTC planning day	scheduled
Spring '27	Production wave 3 example	February 20, 2027	UTC planning day	scheduled
Spring '27	Connected App username-password flow retirement	February 20, 2027	Time zone not specified by source	confirmed

Download the 2026–2027 Salesforce release calendar (PNG)

Embed this chart with credit

Copy this HTML into your page<figure><img src="https://forcefolks.com/img/research/salesforce-release-calendar-2026-2027.png?v=d05c15b95d7b" alt="Winter '27 and Spring '27 planning dates, with a separate OAuth enforcement milestone." width="1800" height="1000" loading="lazy"><figcaption>Chart: <a href="https://forcefolks.com/salesforce-release-dates/">ForceFolks Salesforce Release Calendar</a>. CC BY 4.0.</figcaption></figure>

How to find your Salesforce instance release date

Use your org's instance record for a deployment decision. A general release calendar is useful for planning, but it cannot establish your maintenance window.

1. Open Setup in your Salesforce org.
2. Find Company Information and note the instance name.
3. Open Salesforce Trust Status.
4. Search for that instance and open its maintenance list.
5. Select the major-release record and check its start, end and time zone.
6. Convert that exact window to your team's time zone.
7. Recheck the record before the deployment or test session.

Salesforce's release information page directs admins to Trust for maintenance dates. Use the product-specific status page if your service is not part of the core Salesforce instance schedule.

Record the instance name with the date. Without it, a calendar entry can look precise while describing a different environment. If your org moves to another instance, check the new instance's maintenance schedule.

Salesforce release readiness checklist

Begin with the business processes that must keep working. A successful test needs a clear result, not only a completed task. Record the expected outcome and evidence for each critical process.

• Read the release notes for the products your org uses.
• Confirm which sandbox receives the preview release.
• Save sandbox-only work before any refresh.
• Test key flows, Apex code and scheduled jobs.
• Test integrations with the identities they use in production.
• Check forms, reports and permissions for important user roles.
• Review Release Updates in Setup and identify required action.
• Record failures, owners and the next test date.
• Tell users about changes that affect their daily work.
• Check errors and integration logs after the production upgrade.

Salesforce recommends using the sandbox preview period to test business processes, custom code and integrations. Use its release preparation guidance alongside your own change process. The checklist here is editorial guidance, not proof that your org is ready.

Do not treat a passing sandbox test as permission to skip production checks. Data, users and connected systems can differ between environments. Agree who can approve changes and who will respond if a critical process fails.

How many releases does Salesforce have each year?

Salesforce publishes 3 major seasonal releases: Spring, Summer and Winter. Some products also ship more frequent updates. A major release date does not describe every product update or security enforcement date. See Salesforce's release overview.

Release names and calendar years can differ. Winter '27 starts reaching production in September 2026. Use the complete release name and date when writing a test plan. Do not infer a day from the release name alone.

Release Updates can have separate deadlines. Review their current notes and the status in your org. The OAuth row in this calendar illustrates that distinction. It is not an exhaustive list of security or feature-enforcement deadlines.

For related planning, see the Salesforce implementation checklist, Salesforce admin certification guide and Salesforce events calendar. Conference dates and training dates do not determine your production upgrade window.

How ForceFolks builds the Salesforce Release Calendar

The dataset uses the official release countdown, sandbox instructions, release notes and Salesforce Trust records. Each milestone records its source and check date. Source publication or update dates are stored separately when the source exposes them.

Winter production markers use the Pacific planning days. Sandbox rows retain Salesforce's published date ranges. Spring markers use UTC dates from 4 named instance records. The OAuth retirement retains its published date without an invented time zone.

All ICS entries are all-day planning markers. Their date values match the visible tables. The end date is exclusive, as required by the calendar format.

Entries do not represent service downtime or timed appointments. A 2-day sandbox range remains 2 days in the calendar.

The feed contains 12 entries: 7 Winter milestones, 4 Spring planning examples and 1 security deadline. It does not include guessed Summer '27 dates. CSV, JSON, tables and charts derive from the same reviewed dataset.

The source checks are a snapshot from October 6, 2026. Calendar subscriptions follow your app's refresh behavior. A subscription does not make this page a live Salesforce alert service. Check the source record for current operational information.

Subscribe to the calendar

Subscribe to the calendar

Download the 12-date planning calendar as ICS

Subscription URL for your calendar app

The download is a snapshot. Add the URL as a calendar subscription to receive any later file updates.

Google Calendar links open a prefilled event. Review it before saving. They do not save events automatically.

Salesforce release dates FAQ

More Salesforce research

• Salesforce MCP servers: product roles, access controls and the local DX retirement notice.
• Salesforce admin certification: exam facts and a study planner.
• Salesforce events calendar: upcoming conference dates and calendar exports.
• Dreamforce planning guide: dates and a trip budget calculator.