Who it is for

Better Convex Nuxt fits when Convex is your backend and Nuxt renders pages on the server.

Use it when

• You use Nuxt 4 and want Convex data in the server-rendered HTML.
• Page data must stay live after the page loads.
• You want queries, pagination, mutations, actions, uploads, and connection state as composables.
• You want Better Auth sign-in that works during server rendering.
• Signing out or switching users must never show the previous user's data.
• Nuxt server routes or webhooks must call Convex as the current user.
• You want ChatGPT or Claude to call your Convex functions through MCP.

It still fits when

• Your app renders only in the browser. Set server: false on queries that should not render on the server.
• Your app has no sign-in. Omit convex.auth. The build then contains no auth code.
• You need an imperative call. useConvex() returns query, mutation, action, and onUpdate.

Use something else when

• You use Vue without Nuxt. Use @lupinum/better-convex-vue instead.
• You must support Nuxt 3.
• You want only a thin wrapper around the raw Convex client.
• You want an auth provider other than Better Auth in Nuxt.
• Your code must call setAuth, clearAuth, or close on the Convex client.
• You expect the library to provide roles, billing, or organization workflows.

Typical applications

• Signed-in dashboard. Render the dashboard as the current user, then keep it live. See the protected dashboard recipe.
• Live interface. Chat, feeds, and shared boards show changes without polling. See the real-time feed recipe.
• Public pages with private parts. Render public content for everyone and load private data for signed-in users. See public and private data.
• File workflows. Upload files with progress and cancel, and store their metadata. See the file upload form recipe.

Supported versions

The package's peerDependencies field is the final source. Release compatibility explains how versions change.