JSON to Mongoose Schema Converter

How to use

1. 1Paste a JSON document into the input area, or click Load document sample for a worked example. An array of similar documents also works.
2. 2Set the Schema name (default User). Optionally set a model export identifier and a collection name to override Mongoose's default pluralization.
3. 3Pick ES modules or CommonJS to match your project, then choose 2 or 4 space indent.
4. 4Pick how nested objects are emitted: their own Schema, inline shape, or Schema.Types.Mixed. Use Schema for reusable subdocuments.
5. 5Pick the required mode (all present fields, top level only, or never), toggle timestamps, _id on subdocuments, strict, versionKey, and Date or ObjectId detection.
6. 6Click Copy schema to grab the generated Mongoose code, paste it into your project, and adjust validators or indexes as you go.

About this tool

JSON to Mongoose Schema Converter takes a sample JSON document (or an array of documents) and emits a Mongoose schema and model that match its shape. The inferrer walks the parsed value and maps strings, numbers, booleans, and nested structures to their Mongoose equivalents: String, Number, Boolean, Date for ISO 8601 strings, Schema.Types.ObjectId for 24-character lowercase hex strings, Schema.Types.Mixed when types conflict across samples, and arrays of typed elements or promoted subdocument schemas for arrays of objects. When the root is an array, every element is merged so a key present in some samples becomes non-required and a value type that varies across samples falls back to Mixed; this is how you should hand a sample-set to the converter when you want a schema that accepts every document you have on hand. Nested objects can be promoted into their own named Schema instances (the Mongoose idiom for reusable subdocuments), kept inline next to the parent field, or collapsed into Schema.Types.Mixed when you want flexibility over validation. Naming options cover the schema identifier (which becomes the model name in the registry and the camelCase const for the schema), an optional model export identifier, and an optional collection name override. Module syntax switches between ES modules with import and CommonJS with require to match an existing project. Schema-level options include timestamps for createdAt and updatedAt, versionKey: false to drop __v, strict: false for permissive documents, and _id: false on subdocuments so embedded value objects do not get their own ObjectId. The required heuristic has three modes: every field that is present in every sample, only top-level fields, or never; fields seen as null in any sample always stay optional regardless of the mode. Indent toggles between 2 and 4 spaces. Useful when scaffolding a model from a third-party webhook payload, a Postman response, an existing MongoDB document export, a fixture file, or a record sample from a colleague; or when you want a starting schema for a new collection and have a sketch of the JSON document you plan to store. Parsing, inference, and code generation all run locally in your browser, so the JSON payloads, collection names, and field names you put in here never leave your device.

Free to use. Works in your browser. No signup, no login.