Course contentsShow
← React
Lesson 2219 of 2,39649. Performance: Identifying ProblemsFree lesson

Exporting and Sharing Profiler Data

How to export a profile as JSON for sharing with teammates or analyzing later, and importing profiles back in.

Exporting and Sharing Profiler Data

What you'll learn: How to save React DevTools Profiler recordings as files to share with teammates or analyze later.

The Problem of Ephemeral Profiles

When you record a performance profile in React DevTools, that data only exists in your browser session. The moment you close DevTools or refresh the page, it's gone. But what if you need to share a problematic render pattern with a colleague, or save a baseline profile to compare against future optimizations?

Exporting a Profile

After recording a profile, look for the export button (typically a download icon) in the Profiler toolbar. Clicking it downloads a .json file containing the complete profiling session:

  • All commits recorded
  • Render durations for every component
  • "Why did this render?" data (if enabled in settings)
  • Interaction markers (if using the legacy Interactions API)

Think of this like taking a snapshot of a crime scene—you're preserving all the evidence exactly as it appeared during recording.

Importing a Profile

To analyze an exported profile, click the import button (upload icon) in the Profiler toolbar and select the .json file. The Profiler reconstructs the exact session: flame graphs, ranked charts, commit timings—everything appears as if you'd just recorded it live.

Common Use Cases

  • Async debugging: Record a slow interaction, export it, and analyze it later without time pressure
  • Team collaboration: Share profiles in code reviews or bug reports
  • Before/after comparisons: Export a baseline before optimization, then compare it with a post-fix profile
  • CI integration: Some teams record profiles in automated performance tests and store them as artifacts

Key Takeaway: Exporting profiles to JSON preserves your performance data for sharing and future analysis, turning ephemeral DevTools sessions into permanent diagnostic artifacts.