diff --git a/docs/features/chat-conversations/chat-features/code-execution/artifacts.md b/docs/features/chat-conversations/chat-features/code-execution/artifacts.md
index 5d2bcd2fb..8b70ee2cf 100644
--- a/docs/features/chat-conversations/chat-features/code-execution/artifacts.md
+++ b/docs/features/chat-conversations/chat-features/code-execution/artifacts.md
@@ -32,6 +32,28 @@ When Open WebUI creates an Artifact, you'll see the content displayed in a dedic
 - **Updates**: Open WebUI may update an existing Artifact based on your messages. The Artifact window will display the latest content.
 - **Actions**: Access additional actions for the Artifact, such as copying the content or opening the artifact in full screen, located in the lower right corner of the Artifact.
 
+## Securing Artifact previews with CSP
+
+Artifact HTML previews are rendered inside an iframe. You can now apply a dedicated Content Security Policy (CSP) to those artifact iframes without changing the CSP used by the rest of Open WebUI.
+
+- **Admin setting**: **Admin Panel > Settings > General > Artifacts Content Security Policy**
+- **Environment variable**: [`ARTIFACT_CONTENT_SECURITY_POLICY`](/reference/env-configuration#artifact_content_security_policy)
+- **Default**: Empty, which leaves artifact previews on the browser default policy
+
+When this setting is populated, Open WebUI injects the configured policy into the artifact document before it is rendered. If the artifact already contains a `Content-Security-Policy` meta tag, Open WebUI replaces it with the configured value so the instance-wide artifact policy wins consistently.
+
+Use this when you want to limit what generated artifact HTML can load or execute, for example:
+
+- Block external scripts and network calls for untrusted generated content
+- Allow only the specific image, font, or API origins your artifacts need
+- Apply stricter restrictions to artifacts without tightening the main app's CSP
+
+:::tip
+
+Start permissive and tighten incrementally. Many generated artifacts rely on inline `<script>` and `<style>` tags, so an overly strict policy can make the preview appear blank or partially broken.
+
+:::
+
 ## Editing Artifacts
 
 1. **Targeted Updates**: Describe what you want changed and where. For example:
@@ -112,3 +134,15 @@ If you encounter an issue where the code preview in the chat interface does not
 1. Go to **Settings > Interface**.
 2. Toggle on **Allow Iframe Sandbox Same-Origin Access**.
 3. Save your settings.
+
+### Artifact Preview Is Blank After Setting a CSP
+
+If artifact previews stop rendering after you configure **Artifacts Content Security Policy**, the policy is likely blocking a resource the generated HTML needs.
+
+**What to check:**
+
+1. Open your browser developer tools.
+2. Look for CSP violation messages in the console.
+3. Relax the policy only for the blocked resource types or origins that the artifact requires.
+
+If you want to remove the restriction temporarily, clear **Admin Panel > Settings > General > Artifacts Content Security Policy** or unset `ARTIFACT_CONTENT_SECURITY_POLICY`.
diff --git a/docs/getting-started/advanced-topics/hardening.md b/docs/getting-started/advanced-topics/hardening.md
index 59ac626b5..b8d293044 100644
--- a/docs/getting-started/advanced-topics/hardening.md
+++ b/docs/getting-started/advanced-topics/hardening.md
@@ -218,6 +218,12 @@ If you set a Content Security Policy, start permissive and tighten incrementally
 
 :::
 
+:::note Artifact previews can use a separate CSP
+
+`CONTENT_SECURITY_POLICY` applies to the main Open WebUI app. Artifact HTML previews can be restricted separately with [`ARTIFACT_CONTENT_SECURITY_POLICY`](/reference/env-configuration#artifact_content_security_policy), which injects a CSP directly into artifact iframes. See [Artifacts](/features/chat-conversations/chat-features/code-execution/artifacts#securing-artifact-previews-with-csp).
+
+:::
+
 :::warning Cross-Origin Isolation
 
 Setting `CROSS_ORIGIN_EMBEDDER_POLICY=require-corp` and `CROSS_ORIGIN_OPENER_POLICY=same-origin` together enables cross-origin isolation. This may break resources loaded from third-party origins (e.g., external images, scripts, or iframes) unless those resources explicitly set appropriate CORS headers. Test thoroughly before deploying.
diff --git a/docs/reference/env-configuration.mdx b/docs/reference/env-configuration.mdx
index cded5657e..5cee73bfd 100644
--- a/docs/reference/env-configuration.mdx
+++ b/docs/reference/env-configuration.mdx
@@ -400,6 +400,13 @@ is also being used and set to `True`. **Never disable this if OAUTH/SSO is not b
 - Description: Sets a custom text that will be included when you copy a message in the chat. e.g., `"This text is AI generated"` -> will add "This text is AI generated" to every message, when copied.
 - Persistence: This environment variable is a `PersistentConfig` variable.
 
+#### `ARTIFACT_CONTENT_SECURITY_POLICY`
+
+- Type: `str`
+- Default: Empty string (' ')
+- Description: Sets a dedicated Content Security Policy that Open WebUI injects into artifact iframe previews. If the generated artifact HTML already contains a CSP meta tag, Open WebUI replaces it with this configured value before rendering.
+- Persistence: This environment variable is a `PersistentConfig` variable. It can be configured in the **Admin Panel > Settings > General > Artifacts Content Security Policy**.
+
 #### `THREAD_POOL_SIZE`
 
 - Type: `int`