diff --git a/platform-includes/profiling/browser-profiling/javascript.mdx b/platform-includes/profiling/browser-profiling/javascript.mdx
index 64ed5a4800c8c..006027272058a 100644
--- a/platform-includes/profiling/browser-profiling/javascript.mdx
+++ b/platform-includes/profiling/browser-profiling/javascript.mdx
@@ -46,6 +46,12 @@ Configuration should happen as early as possible in your application's lifecycle
 
 <PlatformContent includePath="profiling/automatic-instrumentation-setup" />
 
+<Alert level="warning" title="Local Profiling with Chrome DevTools">
+
+When you enable `browserProfilingIntegration` in your SDK configuration, Chrome will incorrectly attribute regular rendering work as “Profiling Overhead” if you are doing local profiling via the Chrome DevTools Performance panel. To avoid this, disable or remove the integration when profiling with Chrome DevTools. 
+
+</Alert>
+
 ## The Difference Between DevTools & Sentry's JavaScript Browser Profiler
 
 What does Sentry's JavaScript browser profile offer that Chrome DevTools does not?