JSON to TypeScript Converter

Free tool No sign-up

JSON Input

export interface Root {
  id: number;
  name: string;
  email: string;
  active: boolean;
  roles: ("admin" | "editor")[];
  address: Address;
  lastLogin: string;
  preferences: null;
}

export interface Address {
  city: string;
  zip: string;
}

Root2 types · 10 fields · 0 optional · 1 arrays · 1 enums

About this tool

Paste any JSON and get TypeScript interfaces, Zod schemas, JSON Schema, and Go structs — all four formats from one input, with full inference options.

Why use this converter?

⚡

Faster than asking AI

Paste JSON, see all four output formats instantly — no chat round-trip, no rate limits, no API key. Re-run on a thousand files without burning credits.

🔒

100% in-browser, zero upload

Your JSON never leaves the page. Safe for production payloads, customer data, internal API responses, anything you wouldn't paste into a chat.

🎛️

Real options, not just defaults

Toggle optional inference, enum detection, ISO date detection, type vs interface, exports, parent prefixing — match your team's code style.

↔️

Four formats from one paste

TypeScript, Zod, JSON Schema, and Go — switch between them without re-converting. AI gives you one format per request; this gives you all four.

▶

How to use this converter

Paste your JSON

Drop any JSON object, array, or API response into the left panel. Invalid JSON is flagged inline so you can fix it before reading the output.

Pick a target format

Switch between TypeScript, Zod, JSON Schema, and Go using the tabs above the output. Same input, different shapes — useful when you need types AND a runtime validator.

Tweak the options

Open "More options" to control optionality inference, enum detection, naming style, exports, and Go package name. The output regenerates instantly.

Copy or download

Hit Copy to grab the output or Download to save as a .ts / .json / .go file. Use Share to send the input via a URL hash.

⇄

Output formats at a glance

Format	Best for	What you get
`TypeScript`	Static types, IDE autocomplete	interface or type aliases for every nested object
`Zod`	Runtime validation + types	z.object() schemas with z.infer for matching TS types
`JSON Schema`	OpenAPI specs, form generators	Draft 2020-12 with $defs and $ref for nested types
`Go`	Backend struct definitions	struct types with json:"key,omitempty" tags

What each format looks like

TypeScript

// Input: { "id": 1, "tags": ["a","b"] }
export interface Root {
  id: number;
  tags: string[];
}

Zod

import { z } from 'zod';

export const rootSchema = z.object({
  id: z.number().int(),
  tags: z.array(z.string()),
});
export type Root = z.infer<typeof rootSchema>;

package main

type Root struct {
  ID   int64    `json:"id"`
  Tags []string `json:"tags"`
}

✦

Pro tips

Paste an array of samples for better optionality

Single objects can't reveal which keys are optional. Paste an array of 5–10 real samples — keys missing from any object get marked optional automatically.

Enum threshold tuning

Set "Max enum members" to 0 to disable enum collapsing entirely (every literal becomes a union). Set it to 50 if you have many short value sets like country codes.

Use Zod with TS together

Generate Zod for runtime validation, then enable "Emit z.infer<T>" so your TS types stay in sync with the schema. One source of truth.

Fix Go union fallbacks

Go has no union type, so mixed-type fields become interface{}. Replace these with a wrapper struct + custom UnmarshalJSON when you need real type safety.