Zod nativeEnum in Zod 4

Quick answer: what replaced z.nativeEnum?

In Zod 4, use `z.enum()` for string arrays, enum-like objects, and externally declared TypeScript enums. `z.nativeEnum()` was the Zod 3 API; new Zod 4 code should prefer `z.enum()`.

String enum with z.enum

For most APIs and forms, a string literal enum is clearer than a TypeScript enum. Pass values inline or use `as const` so TypeScript keeps the exact literal union.

const RoleSchema = z.enum(["admin", "editor", "viewer"]);

type Role = z.infer<typeof RoleSchema>;

RoleSchema.parse("admin");

Use as const for reusable arrays

If enum values live in a variable, preserve the literal tuple with `as const`. Without it, TypeScript may widen the array to `string[]` and lose the exact value union.

const statusValues = ["draft", "review", "published"] as const;

const StatusSchema = z.enum(statusValues);

type Status = z.infer<typeof StatusSchema>;

Migrate z.nativeEnum to z.enum

When migrating older Zod 3 code, change the schema constructor and keep tests around the accepted runtime values. Numeric enums and string enums can behave differently, so test the actual values your API sends.

enum Status {
  Draft = "draft",
  Published = "published",
}

// Zod 3 style:
// const StatusSchema = z.nativeEnum(Status);

// Zod 4 style:
const StatusSchema = z.enum(Status);

Enum values vs enum keys

A common nativeEnum mistake is expecting Zod to validate enum member names when the API sends enum values, or the reverse. Decide whether the payload contains `Draft` or `draft`, then model that exact value set.

const ApiStatusSchema = z.enum(["draft", "published"]);

ApiStatusSchema.safeParse("draft"); // success
ApiStatusSchema.safeParse("Draft"); // failure

Exclude or extract enum values

When a form or API route should accept only part of an enum, create a narrower schema with `.exclude()` or `.extract()` instead of adding a vague custom refinement.

const WorkflowStatus = z.enum(["draft", "review", "published", "archived"]);

const EditableStatus = WorkflowStatus.exclude(["archived"]);
const PublicStatus = WorkflowStatus.extract(["published"]);

Generated schemas and enum review

JSON samples can reveal a current enum value, but they cannot prove every allowed value. After using a generator, replace broad strings with explicit `z.enum()` values from product docs, API contracts, or database enums.

Zod enum checklist

Enum bugs are usually value drift bugs. Keep the schema close to the system that owns the allowed values and test the values sent by real payloads.

• Use `z.enum()` for new Zod 4 code.
• Prefer string literal values for API payloads and UI forms.
• Use `.exclude()` or `.extract()` for subsets.
• Add tests for lowercase, uppercase, unknown, and deprecated values.

Zod enum migration map

Use FrameworkKit to generate the starter code, then review the output before shipping it in production.

Zod validation resources

FAQ

Related tools