Update "Share memory|performance traces with more data"

microsoft-edge/dev-videos/index.md

@@ -173,7 +173,7 @@ January 17, 2023
 [![Thumbnail image for video "What's new in DevTools 109"](./index-images/devtools-whatsnew-109.png)](https://www.youtube.com/watch?v=b-q-PLmO-ns)
 
 Covers:
-* Enhanced traces to share memory and performance recordings.
+* Share memory and performance traces with more data.
 * Selector Stats in the **Performance** tool.
 * Track garbage-collected (GC'd) objects in the **Memory** tool.
 * Heap Snapshot visualizer extension.
@@ -183,7 +183,8 @@ Covers:
 
 See also:
 * [What's New in DevTools (Microsoft Edge 109)](../devtools/whats-new/2023/01/devtools-109.md)<!-- has Video section -->
-* [Share enhanced performance and memory traces](../devtools/experimental-features/share-traces.md)
+* [Share a memory trace with more data](../devtools/experimental-features/share-memory-traces.md)
+* [Share a performance trace with more data](../devtools/performance/share-performance-traces.md)
 * [Analyze CSS selector performance during Recalculate Style events](../devtools/performance/selector-stats.md) - selector stats.
 * [Investigate memory allocation, with reduced garbage ("Include objects" checkboxes)](../devtools/rendering-tools/js-runtime.md#investigate-memory-allocation-with-reduced-garbage-include-objects-checkboxes) in _Speed up JavaScript runtime ("Allocation sampling" profiling type)_.
 * [Trash talk: the Orinoco garbage collector](https://v8.dev/blog/trash-talk)

microsoft-edge/devtools/experimental-features/index.md

@@ -557,10 +557,14 @@ Status:
 * This checkbox is present in Microsoft Edge Stable 142.
 
 See also:
-* [Share enhanced performance and memory traces](../experimental-features/share-traces.md)
+* [Share a performance trace with more data](../performance/share-performance-traces.md)
 * [Performance features reference](../performance/reference.md)
 * [Performance recording event reference](../performance/performance-reference.md)
 
+<!--
+the retired term "enhanced traces" remains in this entry for 141, entry then gets removed
+-->
+
 
 <!-- ====================================================================== -->
 ## Performance panel: Enable collecting source text for compiled script
@@ -577,7 +581,7 @@ Status:
 * This checkbox is present in Microsoft Edge Stable 142.
 
 See also:
-* [Share enhanced performance and memory traces](../experimental-features/share-traces.md)
+* [Share a performance trace with more data](../performance/share-performance-traces.md)
 * [Performance features reference](../performance/reference.md)
 * [Performance recording event reference](../performance/performance-reference.md)
 
@@ -595,7 +599,7 @@ Status:
 * This checkbox is present in Microsoft Edge Stable 142.
 
 See also:
-* [Share enhanced performance and memory traces](../experimental-features/share-traces.md)
+* [Share a performance trace with more data](../performance/share-performance-traces.md)
 * [Performance features reference](../performance/reference.md)
 * [Performance recording event reference](../performance/performance-reference.md)
 

microsoft-edge/devtools/experimental-features/share-memory-traces.md

@@ -0,0 +1,178 @@
+---
+title: Share a memory trace with more data
+description: Learn to export and import memory traces with more data in DevTools to resolve low performance and high memory usage issues in your webpages
+author: MSEdgeTeam
+ms.author: msedgedevrel
+ms.topic: article
+ms.service: microsoft-edge
+ms.subservice: devtools
+ms.date: 11/17/2025
+---
+# Share a memory trace with more data
+
+The **Memory** tool records runtime data about your webpage.  Exploring the recorded data makes it possible to improve your webpage's memory usage.
+
+Additionally, the recorded data can be exported to files on disk.  The exported files are called _traces_.
+
+Exporting memory traces is useful when you want to share these files with other people to get help with investigating issues.
+
+
+<!-- ------------------------------ -->
+#### File formats
+
+A trace file can be imported in DevTools at any time.  By default, these traces contain minimal information about the runtime data from the traced webpage.
+
+An exported trace can be a basic `.heapsnapshot`, `.heapprofile`, or `.heaptimeline` file.
+
+A memory trace can also be saved as a `.devtools` file, which contains much more runtime data from the traced webpage.  Advantages of the `.devtools` file format:
+
+* This makes it easier to resolve memory issues, by recreating the environment in which the trace was recorded, and by providing original source files.
+
+* This makes it possible to reliably resolve source code references found in imported traces to the actual runtime code in the **Sources** tool.
+
+* If source maps were present when a trace was recorded, or if they are stored on the [Azure Artifacts Symbol Server](../javascript/consume-source-maps-from-azure.md), it's also possible to resolve code references to their original source code.
+
+
+<!-- ------------------------------ -->
+#### Browser compatibility
+
+* `.heapsnapshot`, `.heapprofile`, and `.heaptimeline` trace files are compatible with Microsoft Edge and other browsers that are based on the Chromium engine.
+
+* `.devtools` traces can only be imported in Microsoft Edge.
+
+
+<!-- ====================================================================== -->
+## Set the default memory trace type
+
+By default, the **Memory** tool exports data as `.heapsnapshot`, `.heapprofile`, or `.heaptimeline` trace files.
+
+To change the default trace type to `.devtools`:
+
+1. Open DevTools by pressing **Ctrl+Shift+I** (Windows, Linux) or **Command+Option+I** (macOS).
+
+1. In DevTools, in the upper right, select **Customize and control DevTools** > **Settings** (![Settings button](./share-memory-traces-images/settings-button-icon.png)).  **Settings** opens, with the **Preferences** page selected.
+
+1. In the **Persistence** section of the **Preferences** page, use the **Export .devtools memory traces** checkbox to control the default type.
+
+   ![The Settings panel in DevTools, showing the export type option](./share-memory-traces-images/set-default-memory-trace-type.png)
+
+
+<!-- ====================================================================== -->
+## Set the export options for memory traces
+
+Memory traces that are `.devtools` files can optionally include console messages, script sources, and DOM elements.
+
+To control whether console messages, script sources, or DOM elements are included in memory traces:
+
+1. Open DevTools by pressing **Ctrl+Shift+I** (Windows, Linux) or **Command+Option+I** (macOS).
+
+1. In DevTools, in the upper right, select **Customize and control DevTools** > **Settings** (![Settings button](./share-memory-traces-images/settings-button-icon.png)).  **Settings** opens, with the **Preferences** page selected.
+
+1. Scroll down to the **Persistence** section:
+
+   ![The Settings panel in DevTools, showing the trace options](./share-memory-traces-images/enhanced-trace-options.png)
+
+1. Use these checkboxes to control what to include:
+
+   * **Include console messages in .devtools memory traces**
+
+   * **Include script sources in .devtools memory traces**
+
+   * **Include DOM snapshots in .devtools memory traces (experimental)**
+
+1. In the upper right of DevTools, click the **Close** (![Close icon](./share-memory-traces-images/close-icon.png)) button.
+
+
+<!-- ====================================================================== -->
+## Export a trace from the Memory tool
+
+To export memory information from the **Memory** tool:
+
+1. Open the **Memory** tool.
+
+1. Select the option button for the type of memory recording you're interested in, such as the **Heap snapshot** option button.
+
+   The following instructions are similar if you choose a different memory recording type, per [Fix memory problems](../memory-problems/index.md).
+
+   **In the case of a heap snapshot:**
+
+1. Click the **Take heap snapshot** (![Take heap snapshot icon](./share-memory-traces-images/take-heap-snapshot-icon.png)) button at top, or the **Take snapshot** button at bottom.
+
+   The snapshot is recorded and displayed.
+
+1. In the toolbar, select the **Save profile** (![Save profile icon](./share-memory-traces-images/save-profile-icon.png)) button:
+
+   ![Microsoft Edge with DevTools, showing the Memory tool, with the Save button](./share-memory-traces-images/exporting-memory-trace.png)
+
+   Or, in the **Memory** tool sidebar, hover over the new snapshot's entry, and then select **Save profile**.
+
+   The **Save As** dialog opens:
+
+   ![The Save As dialog in Windows, showing the memory trace file being saved in a traces folder](./share-memory-traces-images/saving-memory-trace.png)
+
+1. Navigate to a folder in which to save the trace file on your disk.
+
+1. In the **File name** text box, adjust the file name if desired.
+
+1. In the **File name** text box, keep or modify the extension that's specified after the file name.
+
+   <!-- todo: expect the File type dropdown to have not just 1 item, but 2
+
+   when DevTools Settings > **Export .devtools memory traces** checkbox is cleared, **Save as type**'s lone item is 
+   **Performance traces (*.devtools; *.json; *.heapsnapshot)**
+
+   when DevTools Settings > **Export .devtools memory traces** checkbox is selected, **Save as type**'s lone item is 
+   **Performance traces (*.devtools; *.json; *.devtools)**
+   -->
+
+   * `.devtools` includes console messages, script sources, and DOM elements.
+
+   * `.heapsnapshot`, `.heapprofile`, or `.heaptimeline` omits console messages, script sources, and DOM elements.
+
+   Which extension is initially displayed is controlled by a DevTools setting; see [Set the default memory trace type](#set-the-default-memory-trace-type), above.
+
+1. Click the **Save** button.
+
+   The **Save As** dialog closes, and the file is saved to disk.
+
+
+<!-- ====================================================================== -->
+## Import a trace in the Memory tool
+
+To import a trace in the **Memory** tool:
+
+1. Open the **Memory** tool:
+
+   ![Microsoft Edge, showing the Memory tool in DevTools, with the Load button](./share-memory-traces-images/importing-memory-trace.png)
+
+1. Click the **Load profile** (![Load profile icon](./share-memory-traces-images/load-profile-icon.png)) button at the top.  Or, click the **Load profile** button at the bottom.
+
+   The **Open** dialog is displayed.
+
+1. In the lower left dropdown list (a filter), select file types to display:
+
+   * **Performance traces (*.devtools; *.json)** - _Used with the **Performance** tool._
+   * **Heap snapshots (*.devtools; *.heapsnapshot)**
+   * **Heap timelines (*.devtools; *.heaptimeline)**
+   * **Sampled heap profiles (*.devtools; *.heapprofile)**
+
+1. Locate the trace file on your disk, and then select it.
+
+   The trace file is either a `.devtools` file, or a `.heapsnapshot`, `.heaptimeline`, or `.heapprofile` file.
+
+   ![The Windows open dialog, showing a memory trace file](./share-memory-traces-images/opening-memory-trace.png)
+
+1. Click the **Open** button.
+
+   If it's a `.devtools` file, a new DevTools window appears, showing the memory information and the extra runtime information that was recorded displayed in the **Sources**, **Console**, and **Elements** tools.
+
+   Otherwise, the memory information appears in the **Memory** tool, and the rest of the DevTools tabs continue to show information related to the current webpage.
+
+
+<!-- ====================================================================== -->
+## See also
+<!-- all links in article -->
+
+* [Share performance traces with more data](../performance/share-performance-traces.md)<!-- link not in article -->
+* [Fix memory problems](../memory-problems/index.md)
+* [Azure Artifacts Symbol Server](../javascript/consume-source-maps-from-azure.md)