The Locolory toolkit / Developer Toolkit
Convert raw JSON payloads into TypeScript interfaces, type aliases, and runtime Zod validation schemas using private in-browser parsing and inference.
How do you generate TypeScript interfaces from JSON? Parse the JSON recursively, infer primitive and array element types, identify nested object shapes, and emit valid TypeScript declarations or Zod schemas.
No Locolory server upload or conversion API call. Remove secrets and personal data before pasting; device, clipboard, extension, and screenshot risks still apply.
export interface RootObject {
id: number;
name: string;
email?: null;
roles: Array<string>;
profile: RootObjectProfile;
}
export interface RootObjectProfile {
active: boolean;
timezone: string;
}TypeScript checks source code during development but its types are erased at runtime. External JSON can still violate an interface after the application is built.
Zod schemas inspect runtime values and can produce a TypeScript type with z.infer. Generated schemas are a starting point: review constraints, coercion, dates, formats, discriminators and API-version behavior.
| string | string / z.string() |
|---|---|
| number | number / z.number() |
| boolean | boolean / z.boolean() |
| null | null / z.null() |
| array | Array<T> / z.array(T) |
| mixed array | observed union |
| object | nested declaration / z.object |
| empty array | unknown[] or any[] |
Your input shapes the next update
A short note opens in your email app, ready to send to hello@locolory.store.
Locolory does not upload the payload or call an API; conversion occurs in browser memory. Still remove API keys, credentials and personal data because the device, clipboard, extensions, screenshots or local monitoring may expose pasted content.
It creates a union of observed element types. For arrays made entirely of objects, it merges observed keys and marks keys missing from some elements as optional when the optional-fields setting is enabled.
Yes. Nested objects, arrays, primitives, nulls and observed unions produce nested Zod declarations plus an inferred TypeScript type. Generated validation reflects only the supplied sample and should be reviewed against the API contract.
Null is inferred as the null type or z.null(). When optional fields are enabled, nullable fields and keys missing from some object-array elements also receive TypeScript ? or Zod .optional(). Null and missing remain distinct values in the underlying union/schema.