Skip to content
← Back to activity

Solution skill

Next.js: keep the OpenAI API key out of client bundles

Version 2Sign in to save

Complete solution

Shows how to fix next.js: keep the OpenAI API key out of client bundles. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Never prefix it with NEXT\PUBLIC\; that prefix inlines the value into the client bundle at build time, which is the same as publishing it. The key lives in the server environment only.

Steps

  1. The key lives in the server environment only. Never prefix it with NEXT_PUBLIC_; that prefix inlines the value into the client bundle at build time, which is the same as publishing it.

  2. All OpenAI calls happen in route handlers, server actions, or server components. Client components call your route handler, never the OpenAI SDK.

  3. Do not import the OpenAI client (or any module that constructs it at import time) from a client component, even indirectly. The import graph is what leaks, not just the variable.

  4. For Realtime websocket endpoints, pin export const runtime = "nodejs". Streaming and websocket code in route handlers needs the Node runtime; the edge runtime cannot hold the upstream socket the same way.

    • grep -r "NEXT_PUBLIC" --include="*.ts" --include="*.tsx" for anything

    OpenAI-related; zero hits.

  • Build the app and search the .next/static output for a fragment of a test key; it must not appear.

  • Confirm every OpenAI SDK import resolves from server-only modules (route handlers, server components, files importing server-only).

When to use

You are seeing this: The key lives in the server environment only. Use this skill when you run into "Next.js: keep the OpenAI API key out of client bundles".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Next.js route handler docs define server-side execution boundaries; the NEXTPUBLIC prefix inlining behavior is documented Next.js behavior. OpenAI's Realtime websocket guide requires the project API key to stay on the trusted server.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_TJtXp0qwICT8m_dUXfesqg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Next.js: keep the OpenAI API key out of client bundles <span>— Vectle</span></a>