diff --git a/docs/config/build-options.md b/docs/config/build-options.md
index c2c240249c6523..e5c566d2e2bd01 100644
--- a/docs/config/build-options.md
+++ b/docs/config/build-options.md
@@ -181,6 +181,13 @@ When set to `true`, the build will also generate an SSR manifest for determining
 
 Produce SSR-oriented build. The value can be a string to directly specify the SSR entry, or `true`, which requires specifying the SSR entry via `rollupOptions.input`.
 
+## build.ssrEmitAssets
+
+- **Type:** `boolean`
+- **Default:** `false`
+
+During the SSR build, static assets aren't emitted as it is assumed they would be emitted as part of the client build. This option allows frameworks to force emitting them in both the client and SSR build. It is responsability of the framework to merge the assets with a post build step.
+
 ## build.minify
 
 - **Type:** `boolean | 'terser' | 'esbuild'`
diff --git a/packages/vite/src/node/build.ts b/packages/vite/src/node/build.ts
index 9caedc02958aa4..2791313720192e 100644
--- a/packages/vite/src/node/build.ts
+++ b/packages/vite/src/node/build.ts
@@ -223,7 +223,6 @@ export interface BuildOptions {
   ssrManifest?: boolean | string
   /**
    * Emit assets during SSR.
-   * @experimental
    * @default false
    */
   ssrEmitAssets?: boolean