JSON Tools

JSON to Go Struct Converter

Paste JSON, get a Go model for it.

Updated

This tool runs in your browser. No account or signup is required.

Common JSON to Go tasks

Developers typically reach for this page when they need to generate Go structs from JSON; convert API response JSON to Go struct; create Go types with JSON tags. The tool is built for quick, practical work rather than a generic demo.

What matters in a json to go workflow

When developers compare online tools for this job, the useful capabilities tend to center on Go struct tags, nested structs, root naming, type inference. This page keeps those practical needs in mind while linking to related tools when a different workflow is a better fit.

What is JSON to Go?

JSON to Go reads a JSON object and writes a Go type with one field per top-level key. Each field gets a json struct tag.

What problem does it solve?

Typing out model classes by hand for every API response is repetitive. Generating the first draft from a real JSON sample saves the boring part.

How to use JSON to Go

  1. Paste a JSON object into the input box.
  2. Press the convert button.
  3. Copy the generated Go code and adjust names or types to fit your project.

Example

Input

{"id":1,"name":"Ada"}

Go output

type Root struct {
    Id float64 `json:"id"`
    Name string `json:"name"`
}

What you can do with JSON to Go

  • JSON to Go
  • Generate Go class from JSON
  • Go model from JSON

Common use cases

  • Creating models for a new API integration
  • Mocking a type from a sample response
  • Starting a DTO without typing every property

Related developer tasks

  • JSON to Go
  • Generate Go class from JSON
  • Go model from JSON

How JSON maps to Go types

The tool reads the top-level keys of a JSON object and writes one struct field per key. Types come from the sample values you paste:

  • number becomes float64, boolean becomes bool and string becomes string.
  • null, arrays and nested objects become interface{}.
  • Field names are capitalized so they are exported, and each field gets a json tag with the original key.

JSON to Go example

Input:

{"id":1,"name":"Ada","active":true,"address":{"city":"London"},"tags":["math"]}

// Go output
type Root struct {
    Id float64 `json:"id"`
    Name string `json:"name"`
    Active bool `json:"active"`
    Address interface{} `json:"address"`
    Tags interface{} `json:"tags"`
}

What to review before you use the Go output

  • Paste a JSON object, not a bare array. The tool walks the top-level keys, so an array root produces meaningless index names.
  • Nested objects and arrays are not expanded into their own types. In the example, address and tags both fall back to a generic type, so write those types by hand.
  • One sample cannot show which fields are optional or which numbers are integers. Numbers are always mapped to a floating-point type.
  • The json tags let encoding/json match keys correctly even after capitalization. Run gofmt on the result to align the fields.
  • Replace interface{} with real struct or slice types for nested data.

Related: JSON to Java, JSON to TypeScript, JSON Formatter, JSON Validator

JSON to Go FAQ

Does it handle nested objects and arrays?

It maps top-level keys. Nested objects and arrays come out as a generic type (such as object or any), so you will want to refine those by hand.

How are field types chosen?

From the sample values: numbers, booleans and strings get matching types, anything else falls back to a generic type. One sample cannot show whether a field is optional.

Is my data sent to a server?

The processing runs in your browser, so what you paste into the tool is not uploaded for processing. As with any tool, avoid pasting live secrets you cannot afford to leak.

Why is every number a float64?

encoding/json decodes JSON numbers into float64 by default and a sample cannot show whether a value is a whole number. Change it to int where appropriate.

Looking for something else? Browse all developer tools.

onlinedevelopertool.com is a collection of 54 free, browser-based utilities for the small jobs that interrupt real work: formatting a JSON response, decoding a token, converting a timestamp, generating a UUID or checking a hash. Each tool has its own page with a short explanation, a worked example and answers to common questions, so you can use it and learn what it does at the same time.

There is no account to create and nothing to install. Tools run in your browser, so the text you paste is processed on your own device. The one exception is the Website Status Checker, which sends a request from your browser to the address you enter.

Three steps: paste your input, click the tool, copy the result, all inside your browser
Popular developer utilities: JWT decoder, UUID generator, Base64 decoder, SHA-256 hash, regex tester and timestamp converter

What you can do here

  • JSON Tools

    Format, validate, beautify and minify JSON, generate C#, TypeScript, Java, Python, Go, PHP and Kotlin models from it, or convert between JSON, YAML and CSV.

  • Encoders & Decoders

    URL, Base64 and HTML encoding and decoding, plus a JWT decoder for reading token claims.

  • Generators & Hashes

    Generate UUIDs and JWTs, validate UUIDs, and create MD5, SHA-256 and SHA-512 hashes.

  • Web Tools

    Timestamps, color codes, query strings and cron expressions - the small things web work keeps throwing at you.

  • Text & Data

    Format XML and YAML, count text, change case, make slugs, test regex, diff two texts and convert number bases.

  • Website Checking

    Check whether a website or URL is reachable from your browser.

Quick developer reference

  • JSON

    Keys and strings must use double quotes, and trailing commas and comments are not allowed. Those are the three most common reasons a payload fails to parse.

    Validate JSON
  • JWT

    A JSON Web Token is three Base64URL parts joined by dots: header, payload and signature. Decoding shows the claims but does not prove the token is genuine; only signature verification does.

    Decode a JWT
  • Base64

    Base64 is an encoding, not encryption. Anyone can reverse it, and it makes data roughly one third larger, so never use it to hide secrets.

    Decode Base64
  • UUID

    A version 4 UUID is made of random bits and written as 8-4-4-4-12 hexadecimal characters. Collisions are astronomically unlikely, which is why they work well as identifiers.

    Generate a UUID
  • Timestamps

    A Unix timestamp counts time since 1 January 1970 UTC. Ten digits usually means seconds and thirteen digits usually means milliseconds.

    Convert a timestamp
  • Hashes

    MD5 is fine for quick checksums but is not safe for security. Prefer SHA-256 or SHA-512, and remember that hashing is one-way and is not encryption.

    Create a SHA-256 hash

Missing a tool you need? Visit the contact page and tell us what you reach for most often. You can also browse every tool or read the About page to see how the site is built and what it does with your data.