Updates

Author: guardrex

aspnetcore/blazor/components/cascading-values-and-parameters.md

@@ -718,4 +718,4 @@ The following `ExampleTabSet` component uses the `TabSet` component, which conta
 ## Additional resources
 
 * [Generic type support: Explicit generic types based on ancestor components](xref:blazor/components/generic-type-support#explicit-generic-types-based-on-ancestor-components)
-* [State management: Browser storage: Factor out state preservation to a common provider](xref:blazor/state-management/browser-storage#factor-out-state-preservation-to-a-common-provider)
+* [State management: Browser storage: Factor out state preservation to a common provider](xref:blazor/state-management/browser-storage?pivots=server#factor-out-state-preservation-to-a-common-provider)

aspnetcore/blazor/components/integration-hosted-webassembly.md

@@ -549,7 +549,7 @@ The persisted prerendered state is transferred to the client, where it's used to
 
 ## Additional Blazor WebAssembly resources
 
-* [State management: Browser storage: Handle prerendering](xref:blazor/state-management/browser-storage#handle-prerendering)
+* [State management: Browser storage](xref:blazor/state-management/browser-storage?pivots=webassembly)
 * [Prerendering support with assembly lazy loading](xref:blazor/webassembly-lazy-load-assemblies#lazy-load-assemblies-in-a-hosted-blazor-webassembly-solution)
 * Razor component lifecycle subjects that pertain to prerendering
   * [Component initialization (`OnInitialized{Async}`)](xref:blazor/components/lifecycle#component-initialization-oninitializedasync)
@@ -1322,7 +1322,7 @@ Additional work might be required depending on the static resources that compone
 
 ## Additional Blazor WebAssembly resources
 
-* [State management: Browser storage: Handle prerendering](xref:blazor/state-management/browser-storage#handle-prerendering)
+* [State management: Browser storage](xref:blazor/state-management/browser-storage?pivots=webassembly)
 * [Prerendering support with assembly lazy loading](xref:blazor/webassembly-lazy-load-assemblies#lazy-load-assemblies-in-a-hosted-blazor-webassembly-solution)
 * Razor component lifecycle subjects that pertain to prerendering
   * [Component initialization (`OnInitialized{Async}`)](xref:blazor/components/lifecycle#component-initialization-oninitializedasync)

aspnetcore/blazor/components/integration.md

@@ -635,7 +635,7 @@ To resolve the problem, use ***either*** of the following approaches:
 
 ## Additional Blazor Server resources
 
-* [State management: Browser storage: Handle prerendering](xref:blazor/state-management/browser-storage#handle-prerendering)
+* [State management: Browser storage: Handle prerendering](xref:blazor/state-management/browser-storage?pivots=server#handle-prerendering)
 * Razor component lifecycle subjects that pertain to prerendering
   * [Component initialization (`OnInitialized{Async}`)](xref:blazor/components/lifecycle#component-initialization-oninitializedasync)
   * [After component render (`OnAfterRender{Async}`)](xref:blazor/components/lifecycle#after-component-render-onafterrenderasync)
@@ -1154,7 +1154,7 @@ To resolve the problem, use ***either*** of the following approaches:
 
 ## Additional Blazor Server resources
 
-* [State management: Browser storage: Handle prerendering](xref:blazor/state-management/browser-storage#handle-prerendering)
+* [State management: Browser storage: Handle prerendering](xref:blazor/state-management/browser-storage?pivots=server#handle-prerendering)
 * Razor component lifecycle subjects that pertain to prerendering
   * [Component initialization (`OnInitialized{Async}`)](xref:blazor/components/lifecycle#component-initialization-oninitializedasync)
   * [After component render (`OnAfterRender{Async}`)](xref:blazor/components/lifecycle#after-component-render-onafterrenderasync)
@@ -1586,7 +1586,7 @@ To resolve the problem, use ***either*** of the following approaches:
 
 ## Additional Blazor Server resources
 
-* [State management: Browser storage: Handle prerendering](xref:blazor/state-management/browser-storage#handle-prerendering)
+* [State management: Browser storage: Handle prerendering](xref:blazor/state-management/browser-storage?pivots=server#handle-prerendering)
 * Razor component lifecycle subjects that pertain to prerendering
   * [Component initialization (`OnInitialized{Async}`)](xref:blazor/components/lifecycle#component-initialization-oninitializedasync)
   * [After component render (`OnAfterRender{Async}`)](xref:blazor/components/lifecycle#after-component-render-onafterrenderasync)
@@ -2016,7 +2016,7 @@ To resolve the problem, use ***either*** of the following approaches:
 
 ## Additional Blazor Server resources
 
-* [State management: Browser storage: Handle prerendering](xref:blazor/state-management/browser-storage#handle-prerendering)
+* [State management: Browser storage: Handle prerendering](xref:blazor/state-management/browser-storage?pivots=server#handle-prerendering)
 * Razor component lifecycle subjects that pertain to prerendering
   * [Component initialization (`OnInitialized{Async}`)](xref:blazor/components/lifecycle#component-initialization-oninitializedasync)
   * [After component render (`OnAfterRender{Async}`)](xref:blazor/components/lifecycle#after-component-render-onafterrenderasync)

aspnetcore/blazor/components/prerender.md

@@ -422,6 +422,6 @@ Prerendering guidance is organized in the Blazor documentation by subject matter
     * [Secure a SignalR hub](xref:blazor/security/webassembly/additional-scenarios#secure-a-signalr-hub)
   * [Interactive server-side rendering: Cross-site scripting (XSS)](xref:blazor/security/interactive-server-side-rendering#cross-site-scripting-xss)
 
-* [State management: Browser storage: Handle prerendering](xref:blazor/state-management/browser-storage#handle-prerendering): Besides the *Handle prerendering* section, several article sections in the [State management node](xref:blazor/state-management/index) include remarks on prerendering.
+* [State management: Browser storage: Handle prerendering](xref:blazor/state-management/browser-storage?pivots=server#handle-prerendering): Besides the *Handle prerendering* section, several article sections in the [State management node](xref:blazor/state-management/index) include remarks on prerendering.
 
 For .NET 7 or earlier, see [Blazor WebAssembly security additional scenarios: Prerendering with authentication](xref:blazor/security/webassembly/additional-scenarios?view=aspnetcore-7.0&preserve-view=true#prerendering-with-authentication). After viewing the content in this section, reset the documentation article version selector dropdown to the latest .NET release version to ensure that documentation pages load for the latest release on subsequent visits.

aspnetcore/blazor/state-management/browser-storage.md

@@ -5,12 +5,13 @@ description: Learn how to persist user data (state) in Blazor apps using browser
 monikerRange: '>= aspnetcore-3.1'
 ms.author: wpickett
 ms.custom: mvc
-ms.date: 07/31/2025
+ms.date: 08/01/2025
 uid: blazor/state-management/browser-storage
+zone_pivot_groups: blazor-app-models
 ---
-# ASP.NET Core server-side Blazor state management using browser storage
+# ASP.NET Core Blazor state management using browser storage
 
-*This article applies to server-side Blazor apps, Blazor Web Apps and Blazor Server apps. For guidance on Blazor WebAssembly apps, see <xref:blazor/state-management/webassembly#browser-storage>.*
+:::zone pivot="server"
 
 For transient data that the user is actively creating, a commonly used storage location is the browser's [`localStorage`](https://developer.mozilla.org/docs/Web/API/Window/localStorage) and [`sessionStorage`](https://developer.mozilla.org/docs/Web/API/Window/sessionStorage) collections:
 
@@ -499,3 +500,27 @@ In general, the *state provider parent component* pattern is recommended:
 * If there's just one top-level state object to persist.
 
 To persist many different state objects and consume different subsets of objects in different places, it's better to avoid persisting state globally.
+
+:::zone-end
+
+:::zone pivot="webassembly"
+
+For transient data that the user is actively creating, a commonly used storage location is the browser's [`localStorage`](https://developer.mozilla.org/docs/Web/API/Window/localStorage) and [`sessionStorage`](https://developer.mozilla.org/docs/Web/API/Window/sessionStorage) collections:
+
+* `localStorage` is scoped to the browser's instance. If the user reloads the page or closes and reopens the browser, the state persists. If the user opens multiple browser tabs, the state is shared across the tabs. Data persists in `localStorage` until explicitly cleared. The `localStorage` data for a document loaded in a "private browsing" or "incognito" session is cleared when the last "private" tab is closed.
+* `sessionStorage` is scoped to the browser tab. If the user reloads the tab, the state persists. If the user closes the tab or the browser, the state is lost. If the user opens multiple browser tabs, each tab has its own independent version of the data.
+
+> [!NOTE]
+> `localStorage` and `sessionStorage` can be used in Blazor WebAssembly apps but only by writing custom code or using a third-party package.
+
+Generally, `sessionStorage` is safer to use. `sessionStorage` avoids the risk that a user opens multiple tabs and encounters the following:
+
+* Bugs in state storage across tabs.
+* Confusing behavior when a tab overwrites the state of other tabs.
+
+`localStorage` is the better choice if the app must persist state across closing and reopening the browser.
+
+> [!WARNING]
+> Users may view or tamper with the data stored in `localStorage` and `sessionStorage`.
+
+:::zone-end

aspnetcore/blazor/state-management/index.md

@@ -5,19 +5,16 @@ description: Learn how to persist user data (state) in Blazor apps.
 monikerRange: '>= aspnetcore-3.1'
 ms.author: wpickett
 ms.custom: mvc
-ms.date: 07/31/2025
+ms.date: 08/01/2025
 uid: blazor/state-management/index
 ---
 # ASP.NET Core Blazor state management overview
 
-This article and the other articles in this node describe common approaches for maintaining a user's data (state) while they use an app and across browser sessions, including during prerendering on the server.
+This article and the other articles in this node describe common approaches for maintaining a user's data (state) while they use an app and across browser sessions, including during server prerendering.
 
-Guidance specific to server-side Blazor apps, Blazor Web Apps and Blazor Server apps, is provided in the following articles:
+Guidance on using browser storage is provided in <blazor/state-management/browser-storage>.
 
-* <xref:blazor/state-management/server>
-* <blazor/state-management/browser-storage>
-
-Guidance for Blazor WebAssembly apps is covered in <xref:blazor/state-management/webassembly>.
+For guidance specific to server-side Blazor apps, see <xref:blazor/state-management/server>. For Blazor WebAssembly apps, see <xref:blazor/state-management/webassembly>.
 
 The remainder of this article discusses general state management strategies for any type of Blazor app.