import { z } from "zod";
export const UserSchema = z.object({
id: z.string(),
email: z.string().optional(),
role: z.enum(["admin", "editor", "viewer"]),
tags: z.array(z.string()),
profile: z.object({
website: z.string().nullable(),
newsletter: z.boolean(),
}).strict(),
}).strict();
export type User = z.infer<typeof UserSchema>;
Paste a TypeScript interface or type alias and FrameworkKit generates Zod schema starters with inferred TypeScript exports. The ts-to-zod workflow is browser-only and designed for API contracts, DTOs, and form models that need runtime validation.
The converter handles the common shapes developers need first: primitives, optional properties, arrays, nested objects, literal unions, nullable unions, Record<string, T>, and local references.
FrameworkKit does not execute pasted TypeScript. Unsupported language features are surfaced as diagnostics and converted to z.unknown() by default so you can review the boundary explicitly.
Use TypeScript to Zod when your source of truth is an interface or type alias. Use JSON to Zod when your source is a sample API response or fixture.
Generated schemas are starter code. Add business constraints such as email, URL, UUID, min/max, custom refinements, discriminators, and transforms where your actual contract requires them.
Convert TypeScript interface or type alias snippets into copy-ready Zod schemas without uploading code.
Paste a TypeScript interface and generate a reviewable runtime validator starter.
Turn request, response, and domain DTO type aliases into Zod schemas at API boundaries.
Use diagnostics to see where static-only TypeScript features need manual validation decisions.
Use examples, conversion guidance, and validation guides when turning interfaces and type aliases into runtime Zod schemas.
Review interface, type alias, literal union, nullable, Record, and local reference examples.
Learn which TypeScript features convert cleanly and which need manual Zod review.
Use sample JSON instead when your source of truth is a runtime API response or fixture.
Convert finished Zod schemas into portable JSON Schema, AJV, or OpenAPI-compatible output.
Place generated Zod schemas at request and response boundaries in TypeScript apps.
Choose throwing or structured validation results after generating schema starters.
Generate or infer TypeScript types from Zod schemas when Zod is the source of truth.
TypeScript to Zod Converter runs in your browser. FrameworkKit does not send tool input or generated output to a server in the current app.
No. FrameworkKit parses a deterministic subset of interface and type alias syntax in the browser. It does not eval, transpile, import, or run pasted TypeScript.
The v1 converter supports interfaces, object type aliases, primitives, optional properties, arrays, nested object literals, literal unions, nullable unions, Record<string, T>, and references between local declarations.
Generics, mapped types, conditional types, indexed access, imported references, functions, classes, and namespaces are reported with diagnostics and converted to the configured fallback schema.
JSON to Zod infers a schema from sample runtime data. TypeScript to Zod starts from static interfaces or type aliases that already describe the shape you want to validate.
Use it as a starter. Review formats, min/max constraints, discriminators, refinements, and unsupported TypeScript constructs before shipping validation code.