Add instruction for tracing Chrome on desktop

Bug: 149023347
Change-Id: I65eca0aa1275481925ad2d2bbe2785d08368481d
diff --git a/docs/concepts/config.md b/docs/concepts/config.md
index 43082b0..33e94b7 100644
--- a/docs/concepts/config.md
+++ b/docs/concepts/config.md
@@ -7,8 +7,8 @@
 Data sources record data only when one (or more) tracing sessions are active.
 A tracing session is started by invoking the `perfetto` cmdline client and
 passing a config (see QuickStart guide for
-[Android](/docs/quickstart/android-tracing.md) or
-[Linux](/docs/quickstart/linux-tracing.md)).
+[Android](/docs/quickstart/android-tracing.md),
+[Linux](/docs/quickstart/linux-tracing.md), or [Chrome on desktop](/docs/quickstart/chrome-tracing.md)).
 
 A simple trace config looks like this:
 
diff --git a/docs/images/record-trace-chrome.png b/docs/images/record-trace-chrome.png
new file mode 100644
index 0000000..a18d890
--- /dev/null
+++ b/docs/images/record-trace-chrome.png
Binary files differ
diff --git a/docs/images/tracing-categories-chrome.png b/docs/images/tracing-categories-chrome.png
new file mode 100644
index 0000000..16703f6
--- /dev/null
+++ b/docs/images/tracing-categories-chrome.png
Binary files differ
diff --git a/docs/quickstart/chrome-tracing.md b/docs/quickstart/chrome-tracing.md
new file mode 100644
index 0000000..4e17172
--- /dev/null
+++ b/docs/quickstart/chrome-tracing.md
@@ -0,0 +1,39 @@
+# Quickstart: Record traces on Chrome desktop
+
+Perfetto can capture traces right from the Chrome browser on desktop. It captures traces across all open tabs.
+
+> To record traces from Chrome on Android, follow the [instructions for recording Android system traces](/docs/quickstart/android-tracing.md) and enable the Chrome probe.
+
+## Recording a trace
+
+1. Navigate to [ui.perfetto.dev](https://ui.perfetto.dev/) and select **"Record new trace"** from the left menu.
+    > If you are using the Perfetto UI for the first time, you have to install the [Perfetto UI Chrome extension](https://chrome.google.com/webstore/detail/perfetto-ui/lfmkphfpdbjijhpomgecfikhfohaoine).
+2. Select **"Chrome"** as **"Target platform"** in the drop-down.
+
+   On Chrome OS, you can also record system traces by selecting the "Chrome OS (system trace)" target platform.
+3. Сonfigure settings in **"Recording settings"**.
+
+   ![Record page of the Perfetto UI](/docs/images/record-trace-chrome.png)
+
+    >Note: "Long trace" mode is not yet available for Chrome desktop.
+
+    > Tips:
+    >
+    > - To save the current config settings and apply them later go to the "Saved configs" menu.
+    > - To share your config settings go to the "Recording command" menu.
+>
+4. Select which categories (or top level tags) in the **Chrome** probe section that you want.
+
+   > Note: The tags at the top enable groups of related categories, but there is currently no direct way to see them when targeting Chrome. However, you can switch the target to "Android" and then see the categories in the generated config in the "Recording Command" section if you are curious.
+
+   The list at the bottom can be used to select additional categories.
+
+   ![Tracing categories of Chrome](/docs/images/tracing-categories-chrome.png)
+5. Now you can start the trace recording. Press the **"Start recording"** button when ready.
+6. Proceed to use the browser to capture the action you want to trace, and wait for the trace to finish. You can also stop the trace manually by pressing the "Stop" button.
+
+   **Do not close the perfetto UI tab!** Otherwise, tracing will stop and the trace data will be lost.
+
+7. Once the trace is ready, you can find and analyze it in the left menu **"Current Trace"**.
+
+    > **IMPORTANT**: If you want to share a trace, keep in mind that it will contain the URL and title of all open tabs, URLs of subresources used by each tab, extension IDs, hardware identifying details, and other similar information that you may not want to make public.
diff --git a/docs/toc.md b/docs/toc.md
index be3b621..5c1abd9 100644
--- a/docs/toc.md
+++ b/docs/toc.md
@@ -3,6 +3,7 @@
 * [Quickstart](#)
   * [Record traces on Android](quickstart/android-tracing.md)
   * [Record traces on Linux](quickstart/linux-tracing.md)
+  * [Record Chrome traces](quickstart/chrome-tracing.md)
   * [SQL analysis and metrics](quickstart/trace-analysis.md)
   * [Trace conversion](quickstart/traceconv.md)
   * [Heap profiling](quickstart/heap-profiling.md)