diff --git a/tutorials/export/exporting_for_web.rst b/tutorials/export/exporting_for_web.rst
index 42c1d0a9f1c..f87d8ec12c6 100644
--- a/tutorials/export/exporting_for_web.rst
+++ b/tutorials/export/exporting_for_web.rst
@@ -453,6 +453,46 @@ the export menu.
    * - Encryption / Encryption Key
      - ``GODOT_SCRIPT_ENCRYPTION_KEY``
 
+.. _doc_exporting_for_web_troubleshooting:
+
+Troubleshooting
+---------------
+
+Running the export locally shows another project instead
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If you use one-click deploy in multiple projects, you may notice that one
+of the projects you've previously deployed is shown instead of the project
+you're currently working on. This is due to service worker caching which
+currently lacks an automated cache busting mechanism.
+
+As a workaround, you can manually unregister the current service worker
+so that the cache is reset. This also allows a new service worker to be registered.
+In Chromium-based browsers, open the Developer Tools by pressing
+:kbd:`F12` or :kbd:`Ctrl + Shift + I` (:kbd:`Cmd + Option + I` on macOS),
+then click on the Application tab in DevTools (it may be hidden behind a chevron
+icon if the devtools pane is narrow). You can either check
+:button:`Update on reload` and reload the page, or click :button:`Unregister`
+next to the service worker that is currently registered, then reload the page.
+
+.. figure:: img/exporting_for_web_reset_unregister_service_worker_chromium.webp
+   :align: center
+   :alt: Unregistering the service worker in Chromium-based browsers' DevTools
+
+   Unregistering the service worker in Chromium-based browsers' DevTools
+
+The procedure is similar in Firefox. Open developer tools by pressing
+:kbd:`F12` or :kbd:`Ctrl + Shift + I` (:kbd:`Cmd + Option + I` on macOS),
+click on the Application tab in DevTools (it may be hidden behind a chevron
+icon if the devtools pane is narrow). Click :button:`Unregister` next to the
+service worker that is currently registered, then reload the page.
+
+.. figure:: img/exporting_for_web_reset_unregister_service_worker_firefox.webp
+   :align: center
+   :alt: Unregistering the service worker in Firefox's DevTools
+
+   Unregistering the service worker in Firefox's DevTools
+
 Export options
 --------------
 
diff --git a/tutorials/export/img/exporting_for_web_reset_unregister_service_worker_chromium.webp b/tutorials/export/img/exporting_for_web_reset_unregister_service_worker_chromium.webp
new file mode 100644
index 00000000000..b645c9ed1fb
Binary files /dev/null and b/tutorials/export/img/exporting_for_web_reset_unregister_service_worker_chromium.webp differ
diff --git a/tutorials/export/img/exporting_for_web_reset_unregister_service_worker_firefox.webp b/tutorials/export/img/exporting_for_web_reset_unregister_service_worker_firefox.webp
new file mode 100644
index 00000000000..b039a15487e
Binary files /dev/null and b/tutorials/export/img/exporting_for_web_reset_unregister_service_worker_firefox.webp differ
diff --git a/tutorials/export/one-click_deploy.rst b/tutorials/export/one-click_deploy.rst
index d67738a3034..f57f8143a18 100644
--- a/tutorials/export/one-click_deploy.rst
+++ b/tutorials/export/one-click_deploy.rst
@@ -157,3 +157,11 @@ Web > Use TLS**.
     the paths to the key and certificate files in the **Export > Web > TLS Key**
     and **Export > Web > TLS Certificate**. This will only work if the project
     is accessed through a domain name that is part of the TLS certificate.
+
+.. warning::
+
+    When using one-click deploy on different projects, it's possible that
+    a previously edited project is being shown instead. This is due to service
+    worker caching not being cleared automatically. See
+    :ref:`doc_exporting_for_web_troubleshooting` for instructions on unregistering
+    the service worker, which will effectively clear the cache and resolve the issue.