Fast JSON encoder/decoder compatible with encoding/json for Go



Go GoDoc codecov

Fast JSON encoder/decoder compatible with encoding/json for Go


go get

How to use

Replace import statement from encoding/json to

-import "encoding/json"
+import ""

JSON library comparison

name encoder decoder compatible with encoding/json
encoding/json yes yes N/A
json-iterator/go yes yes partial
easyjson yes yes no
gojay yes yes no
segmentio/encoding/json yes yes yes
jettison yes no no
simdjson-go no yes no
goccy/go-json yes yes yes
  • json-iterator/go isn't compatible with encoding/json in many ways, but it hasn't been supported for a long time.


$ cd benchmarks
$ go test -bench .



How it works

go-json is very fast in both encoding and decoding compared to other libraries. It's easier to implement by using automatic code generation for performance or by using a dedicated interface, but go-json dares to stick to compatibility with encoding/json and is the simple interface. Despite this, we are developing with the aim of being the fastest library.

Here, we explain the various speed-up techniques implemented by go-json.

Basic technique

The techniques listed here are the ones used by most of the libraries listed above.

Buffer reuse

Since the only value required for the result of json.Marshal(interface{}) ([]byte, error) is []byte, the only value that must be allocated during encoding is the return value []byte .

Also, as the number of allocations increases, the performance will be affected, so the number of allocations should be kept as low as possible when creating []byte.

Therefore, there is a technique to reduce the number of times a new buffer must be allocated by reusing the buffer used for the previous encoding by using sync.Pool.

Finally, you allocate a buffer that is as long as the resulting buffer and copy the contents into it, you only need to allocate the buffer once in theory.

type buffer struct {
    data []byte

var bufPool = sync.Pool{
    New: func() interface{} {
        return &buffer{data: make([]byte, 0, 1024)}

buf := bufPool.Get().(*buffer)
data := encode( // reuse

newBuf := make([]byte, len(data))
copy(newBuf, buf) = data

Elimination of reflection

As you know, the reflection operation is very slow.

Therefore, using the fact that the address position where the type information is stored is fixed for each binary ( we call this typeptr ), we can use the address in the type information to call a pre-built optimized process.

For example, you can get the address to the type information from interface{} as follows and you can use that information to call a process that does not have reflection.

To process without reflection, pass a pointer (unsafe.Pointer) to the value is stored.

type emptyInterface struct {
    typ unsafe.Pointer
    ptr unsafe.Pointer

var typeToEncoder = map[uintptr]func(unsafe.Pointer)([]byte, error){}

func Marshal(v interface{}) ([]byte, error) {
    iface := (*emptyInterface)(unsafe.Pointer(&v)
    typeptr := uintptr(iface.typ)
    if enc, exists := typeToEncoder[typeptr]; exists {
        return enc(iface.ptr)

※ In reality, typeToEncoder can be referenced by multiple goroutines, so exclusive control is required.

Unique speed-up technique


Do not escape arguments of Marshal

json.Marshal and json.Unmarshal receive interface{} value and they perform type determination dynamically to process. In normal case, you need to use the reflect library to determine the type dynamically, but since reflect.Type is defined as interface, when you call the method of reflect.Type, The reflect's argument is escaped.

Therefore, the arguments for Marshal and Unmarshal are always escape to the heap. However, go-json can use the feature of reflect.Type while avoiding escaping.

reflect.Type is defined as interface, but in reality reflect.Type is implemented only by the structure rtype defined in the reflect package. For this reason, to date reflect.Type is the same as *reflect.rtype.

Therefore, by directly handling *reflect.rtype, which is an implementation of reflect.Type, it is possible to avoid escaping because it changes from interface to using struct.

The technique for working with *reflect.rtype directly from go-json is implemented at

Also, the same technique is cut out as a library ( )

Initially this feature was the default behavior of go-json. But after careful testing, I found that I passed a large value to json.Marshal() and if the argument could not be assigned to the stack, it could not be properly escaped to the heap (a bug in the Go compiler).

Therefore, this feature will be provided as an optional until this issue is resolved.

To use it, add NoEscape like MarshalNoEscape()

Encoding using opcode sequence

I explained that you can use typeptr to call a pre-built process from type information.

In other libraries, this dedicated process is processed by making it an function calling like anonymous function, but function calls are inherently slow processes and should be avoided as much as possible.

Therefore, go-json adopted the Instruction-based execution processing system, which is also used to implement virtual machines for programming language.

If it is the first type to encode, create the opcode ( instruction ) sequence required for encoding. From the second time onward, use typeptr to get the cached pre-built opcode sequence and encode it based on it. An example of the opcode sequence is shown below.

    X int `json:"x"`
    Y string `json:"y"`
}{X: 1, Y: "hello"})

When encoding a structure like the one above, create a sequence of opcodes like this:

- opStructFieldHead ( `{` )
- opStructFieldInt ( `"x": 1,` )
- opStructFieldString ( `"y": "hello"` )
- opStructEnd ( `}` )
- opEnd

※ When processing each operation, write the letters on the right.

In addition, each opcode is managed by the following structure ( Pseudo code ).

type opType int
const (
    opStructFieldHead opType = iota
type opcode struct {
    op opType
    key []byte
    next *opcode

The process of encoding using the opcode sequence is roughly implemented as follows.

func encode(code *opcode, b []byte, p unsafe.Pointer) ([]byte, error) {
    for {
        switch code.op {
        case opStructFieldHead:
            b = append(b, '{')
            code =
        case opStructFieldInt:
            b = append(b, code.key...)
            b = appendInt((*int)(unsafe.Pointer(uintptr(p)+code.offset)))
            code =
        case opStructFieldString:
            b = append(b, code.key...)
            b = appendString((*string)(unsafe.Pointer(uintptr(p)+code.offset)))
            code =
        case opStructEnd:
            b = append(b, '}')
            code =
        case opEnd:
            goto END
    return b, nil

In this way, the huge switch-case is used to encode by manipulating the linked list opcodes to avoid unnecessary function calls.

Opcode sequence optimization

One of the advantages of encoding using the opcode sequence is the ease of optimization. The opcode sequence mentioned above is actually converted into the following optimized operations and used.

- opStructFieldHeadInt ( `{"x": 1,` )
- opStructEndString ( `"y": "hello"}` )
- opEnd

It has been reduced from 5 opcodes to 3 opcodes ! Reducing the number of opcodees means reducing the number of branches with switch-case. In other words, the closer the number of operations is to 1, the faster the processing can be performed.

In go-json, optimization to reduce the number of opcodes itself like the above and it speeds up by preparing opcodes with optimized paths.

Change recursive call from CALL to JMP

Recursive processing is required during encoding if the type is defined recursively as follows:

type T struct {
    X int
    U *U

type U struct {
    T *T

b, err := json.Marshal(&T{
    X: 1,
    U: &U{
        T: &T{
            X: 2,
fmt.Println(string(b)) // {"X":1,"U":{"T":{"X":2,"U":null}}}

In go-json, recursive processing is processed by the operation type of opStructFieldRecursive.

In this operation, after acquiring the opcode sequence used for recursive processing, the function is not called recursively as it is, but the necessary values ​​are saved by itself and implemented by moving to the next operation.

The technique of implementing recursive processing with the JMP operation while avoiding the CALL operation is a famous technique for implementing a high-speed virtual machine.

For more details, please refer to the article ( but Japanese only ).

Dispatch by typeptr from map to slice

When retrieving the data cached from the type information by typeptr, we usually use map. Map requires exclusive control, so use sync.Map for a naive implementation.

However, this is slow, so it's a good idea to use the atomic package for exclusive control as implemented by segmentio/encoding/json ( ).

This implementation slows down the set instead of speeding up the get, but it works well because of the nature of the library, it encodes much more for the same type.

However, as a result of profiling, I noticed that runtime.mapaccess2 accounts for a significant percentage of the execution time. So I thought if I could change the lookup from map to slice.

There is an API named typelinks defined in the runtime package that the reflect package uses internally. This allows you to get all the type information defined in the binary at runtime.

The fact that all type information can be acquired means that by constructing slices in advance with the acquired total number of type information, it is possible to look up with the value of typeptr without worrying about out-of-range access.

However, if there is too much type information, it will use a lot of memory, so by default we will only use this optimization if the slice size fits within 2Mib .

If this approach is not available, it will fall back to the atomic based process described above.

If you want to know more, please refer to the implementation here


Dispatch by typeptr from map to slice

Like the encoder, the decoder also uses typeptr to call the dedicated process.

Faster termination character inspection using NUL character

In order to decode, you have to traverse the input buffer character by position. At that time, if you check whether the buffer has reached the end, it will be very slow.

buf : []byte type variable. holds the string passed to the decoder cursor : int64 type variable. holds the current read position

buflen := len(buf)
for ; cursor < buflen; cursor++ { // compare cursor and buflen at all times, it is so slow.
    switch buf[cursor] {
    case ' ', '\n', '\r', '\t':

Therefore, by adding the NUL (\000) character to the end of the read buffer as shown below, it is possible to check the termination character at the same time as other characters.

for {
    switch buf[cursor] {
    case ' ', '\n', '\r', '\t':
    case '\000':
        return nil

Use Boundary Check Elimination

Due to the NUL character optimization, the Go compiler does a boundary check every time, even though buf[cursor] does not cause out-of-range access.

Therefore, go-json eliminates boundary check by fetching characters for hotspot by pointer operation. For example, the following code.

func char(ptr unsafe.Pointer, offset int64) byte {
	return *(*byte)(unsafe.Pointer(uintptr(ptr) + uintptr(offset)))

p := (*sliceHeader)(&unsafe.Pointer(buf)).data
for {
    switch char(p, cursor) {
    case ' ', '\n', '\r', '\t':
    case '\000':
        return nil

Checking the existence of fields of struct using Bitmaps

I found by the profiling result, in the struct decode, lookup process for field was taking a long time.

For example, consider decoding a string like {"a":1,"b":2,"c":3} into the following structure:

type T struct {
    A int `json:"a"`
    B int `json:"b"`
    C int `json:"c"`

At this time, it was found that it takes a lot of time to acquire the decoding process corresponding to the field from the field name as shown below during the decoding process.

fieldName := decodeKey(buf, cursor) // "a" or "b" or "c"
decoder, exists := fieldToDecoderMap[fieldName] // so slow
if exists {
    decoder(buf, cursor)
} else {
    skipValue(buf, cursor)

To improve this process, json-iterator/go is optimized so that it can be branched by switch-case when the number of fields in the structure is 10 or less (switch-case is faster than map). However, there is a risk of hash collision because the value hashed by the FNV algorithm is used for conditional branching. Also, gojay processes this part at high speed by letting the library user yourself write switch-case.

go-json considers and implements a new approach that is different from these. I call this bitmap field optimization.

The range of values ​​per character can be represented by [256]byte. Also, if the number of fields in the structure is 8 or less, int8 type can represent the state of each field. In other words, it has the following structure.

  • Base ( 8bit ): 00000000
  • Key "a": 00000001 ( assign key "a" to the first bit )
  • Key "b": 00000010 ( assign key "b" to the second bit )
  • Key "c": 00000100 ( assign key "c" to the third bit )

Bitmap structure is the following

        | key index(0) |
 0      | 00000000     |
 1      | 00000000     |
~~      |              |
97 (a)  | 00000001     |
98 (b)  | 00000010     |
99 (c)  | 00000100     |
~~      |              |
255     | 00000000     |

You can think of this as a Bitmap with a height of 256 and a width of the maximum string length in the field name. In other words, it can be represented by the following type .


When decoding a field character, check whether the corresponding character exists by referring to the pre-built bitmap like the following.

var curBit int8 = math.MaxInt8 // 11111111

c := char(buf, cursor)
bit := bitmap[keyIdx][c]
curBit &= bit
if curBit == 0 {
    // not found field

If curBit is not 0 until the end of the field string, then the string is You may have hit one of the fields. But the possibility is that if the decoded string is shorter than the field string, you will get a false hit.

  • input: {"a":1}
type T struct {
    X int `json:"abc"`

※ Since a is shorter than abc, it can decode to the end of the field character without curBit being 0.

Rest assured. In this case, it doesn't matter because you can tell if you hit by comparing the string length of a with the string length of abc.

Finally, calculate the position of the bit where 1 is set and get the corresponding value, and you're done.

Using this technique, field lookups are possible with only bitwise operations and access to slices.

go-json uses a similar technique for fields with 9 or more and 16 or less fields. At this time, Bitmap is constructed as [maxKeyLen][256]int16 type.

Currently, this optimization is not performed when the maximum length of the field name is long (specifically, 64 bytes or more) in addition to the limitation of the number of fields from the viewpoint of saving memory usage.


I have done a lot of other optimizations. I will find time to write about them. If you have any questions about what's written here or other optimizations, please visit the #go-json channel on .


Regarding the story of go-json, there are the following articles in Japanese only.



  • Defferent behavior from

    Defferent behavior from "encoding/json" for MarshalJSON

    package main
    import (
    	goccyjson ""
    func main() {
    	v := []struct{
    		NS NullString
    			NS: NullString{String:"test", Valid: true},
    	got, _ := json.Marshal(v)
    	fmt.Println(string(got)) // output: [{"NS":"test"}]
    	got, _ = goccyjson.Marshal(v)
    	fmt.Println(string(got)) // output: [{"NS":{"String":"test","Valid":true}}]
    type NullString sql.NullString
    func (s *NullString) MarshalJSON() ([]byte, error) {
    	if !s.Valid {
    		return json.Marshal(nil)
    	return json.Marshal(s.String)

    When I change (s *NullString) to (s NullString), it's fine. (and maybe I should do so.) So, it is not a critical issue, but I would prefer that compatibility be supported.

    opened by hidechae 0
  • Next Optimization Plan

    Next Optimization Plan

    Here are some optimization ideas that I'm currently thinking about

    1. Optimization for standard library's Marshal(JSON|Text) and Unmarshal(JSON|Text)

    The standard library's Marshaler returns valid and (compacted) JSON, so we can omit validation and compaction process for specified types e.g.) time.Time net.IP big.Float Similarly, json.RawMessage can be optimized .

    2. Using unsafe.Add since Go 1.17

    Since we can use more optimized instructions by using unsafe.Add, It can be expected that the speed of the part where pointer calculation is performed will be increased.

    3. Add unordered option for struct fields when encoding

    By adding the unordered option, encoding of the same type can be processed at once, which improves the execution efficiency of the VM. In some cases, tail-recursive optimization can be used in recursive instructions and interface instructions.

    4. Opcode's design with CPU cache in mind

    Adjusting the size of the structure used at the time of encoding makes it easier to be placed in the CPU cache.

    enhancement performance 
    opened by goccy 0
  • Support multiple conversion types

    Support multiple conversion types

    Hi, Now with introduction of generics Maybe it will be worthy to support multiple json values parsers for same key

    i.e If we have field of bool It will accept both: true “true”

    same for numbers If i take example from Java Json parsers can parse both types(base type, and conversion from string)

    feature request 
    opened by itzikiusa 2
  • crashed by anonymous structure field

    crashed by anonymous structure field

    Hi guys, strange behavior happened. go-json crashed in the following code, whereas the stand library works correctly

    package go_benchmark
    import (
    	gojson ""
    type InnerBigInt struct{
    	 *big.Int `json:"int"`
    type TextureBigInt struct {
    	Amount InnerBigInt	`json:"amount"`
    func TestAnonymousField(t *testing.T) {
    	multiplier := new(big.Int).Exp(big.NewInt(10), big.NewInt(18), nil)
    	bigIntAmount := new(big.Int).Mul(big.NewInt(10000), multiplier)
    	bt := TextureBigInt{
    opened by lisuxiaoqi 2
  • Option to match JS/ECMA behavior for NaN and Inf

    Option to match JS/ECMA behavior for NaN and Inf

    Would it be possible to add an option to MarshalWithOption which mimics the standard JS behavior of marshalling NaN and Inf to null, rather than returning an error?

    For reference: (step 9)

    feature request 
    opened by clecompt-msft 0
  • Different behavior from

    Different behavior from "encoding/json"

    package main
    import (
    	gojson ""
    type Media []*Image
    type Image struct {
    	Pos      Pos    `json:"pos"`
    	OldURL   string `json:"old_url"`
    	FileName string `json:"file_name"`
    	URL      string `json:"url"`
    type BlockType struct {
    	Tag string `json:"tag"`
    type Blocks struct {
    	Points    string    `json:"points"`
    	BlockURL  string    `json:"block_url"`
    	Result    string    `json:"result"`
    	OldResult int       `json:"old_result"`
    	Angle     int       `json:"angle"`
    	BlockType BlockType `json:"block_type"`
    type Pos struct {
    	Blocks []Blocks `json:"blocks"`
    	Angle  int      `json:"angle"`
    func main() {
    	var a Media
    	err := gojson.Unmarshal([]byte(`[{"url":"8621_E4B5B8C2A88E456CSR7TX7h6.jpg","old_url":"8621_E4B5B8C2A88E456CSR7TX7h6.jpg","file_name":"8621_E4B5B8C2A88E456CSR7TX7h6.jpg","pos":{"blocks":{}}},{"url":"8621_94AC337652D44DBDDR7rY93K.jpg","old_url":"8621_94AC337652D44DBDDR7rY93K.jpg","file_name":"8621_94AC337652D44DBDDR7rY93K.jpg","pos":{"angle":0,"blocks":[{"angle":0,"old_result":2,"result":"wrong","block_type":{"tag":"1_1_1"},"points":"242,199,322,198,321,296,241,297"}]}}]`), &a)
    	fmt.Println(err)  // output:  json: slice unexpected end of JSON input
    	fmt.Println(a)    // output:  []
    	var a1 Media
    	err = json.Unmarshal([]byte(`[{"url":"8621_E4B5B8C2A88E456CSR7TX7h6.jpg","old_url":"8621_E4B5B8C2A88E456CSR7TX7h6.jpg","file_name":"8621_E4B5B8C2A88E456CSR7TX7h6.jpg","pos":{"blocks":{}}},{"url":"8621_94AC337652D44DBDDR7rY93K.jpg","old_url":"8621_94AC337652D44DBDDR7rY93K.jpg","file_name":"8621_94AC337652D44DBDDR7rY93K.jpg","pos":{"angle":0,"blocks":[{"angle":0,"old_result":2,"result":"wrong","block_type":{"tag":"1_1_1"},"points":"242,199,322,198,321,296,241,297"}]}}]`), &a1)
    	fmt.Println(err)    // output:    cannot unmarshal object into Go struct field Pos.pos.blocks of type []main.Blocks
    	fmt.Println(a1)     // output:    [0xc0000fc460 0xc0000fc500]
    opened by hoslo 1
  • v0.9.7(Apr 21, 2022)

    What's Changed

    • fix: an incompatible behavior on map key decoder by @orisano in
    • fix: add filtering on slow path by @orisano in
    • feat: add DebugWith option by @orisano in
    • fix: add a fallback uint8 sliceDecoder to bytesDecoder by @orisano in
    • fix: to care about the case of OpInterfacePtr by @orisano in

    Full Changelog:

    Source code(tar.gz)
    Source code(zip)
  • v0.9.6(Mar 22, 2022)

    What's Changed

    • fix: to care ints minimum values by @orisano in
    • Update go version by @goccy in
    • feat: improves escapeString's performance by @orisano in
    • fix: to safe when got unexpected typeptr by @orisano in
    • fix: mismatched between len(s.buf) and s.bufSize by @orisano in

    Full Changelog:

    Source code(tar.gz)
    Source code(zip)
  • v0.9.5(Mar 4, 2022)

    What's Changed

    • fix: panic when decoding time.Time with context by @orisano in
    • fix: incorrect handling on skipValue by @orisano in
    • fix: avoid reading the next character in buffer to nul consideration by @orisano in
    • feat: improve performance when a payload contains escape sequence by @orisano in

    Full Changelog:

    Source code(tar.gz)
    Source code(zip)
  • v0.9.4(Jan 20, 2022)

    What's Changed

    • Fix IsNilForMarshaler for string type with omitempty by @IncSW in
    • Fix the case where the embedded field is at the end by @goccy in

    Full Changelog:

    Source code(tar.gz)
    Source code(zip)
  • v0.9.3(Jan 14, 2022)

    What's Changed

    • Fix logic of removing struct field for decoder by @goccy in

    Full Changelog:

    Source code(tar.gz)
    Source code(zip)
  • v0.9.2(Jan 14, 2022)

    What's Changed

    • Add invalid decoder to delay type error judgment at decode by @goccy in

    Full Changelog:

    Source code(tar.gz)
    Source code(zip)
  • v0.9.1(Jan 11, 2022)

    What's Changed

    • Fix encoding of MarshalText/MarshalJSON operation with head offset by @goccy in

    Full Changelog:

    Source code(tar.gz)
    Source code(zip)
  • v0.9.0(Jan 5, 2022)

    New feature

    • Supports dynamic filtering of struct fields ( #314 )

    Improve encoding performance

    • Improve map encoding performance ( #310 )
    • Optimize encoding path for escaped string ( #311 )
    • Add encoding option for performance ( #312 )

    Fix bugs

    • Fix panic at encoding map value on 1.18 ( #310 )
    • Fix MarshalIndent for interface type ( #317 )
    Source code(tar.gz)
    Source code(zip)
  • v0.8.1(Dec 5, 2021)

    What's Changed

    • Fix operation conversion for PtrHead to Head in Recursive type by @goccy in

    Full Changelog:

    Source code(tar.gz)
    Source code(zip)
  • v0.8.0(Dec 2, 2021)

    What's Changed

    • Fix embedded field conflict behavior by @goccy in
    • Refactor compiler for encoder by @goccy in
    • Refactor vm code for encoder by @goccy in

    Full Changelog:

    Source code(tar.gz)
    Source code(zip)
  • v0.7.10(Oct 16, 2021)

    What's Changed

    • Fix conversion from pointer to uint64 by @goccy in

    Full Changelog:

    Source code(tar.gz)
    Source code(zip)
  • v0.7.9(Sep 28, 2021)

  • v0.7.8(Sep 1, 2021)

    • Fix mapassign_faststr for indirect struct type ( #283 )
    • Fix encoding of not empty interface type ( #284 )
    • Fix encoding of empty struct interface type ( #286 )
    Source code(tar.gz)
    Source code(zip)
  • v0.7.7(Aug 25, 2021)

  • v0.7.6(Aug 13, 2021)

  • v0.7.5(Aug 12, 2021)

    • Fix encoding of embedded struct with tags ( #265 )
    • Fix encoding of embedded struct that isn't first field ( #272 )
    • Fix decoding of binary type with escaped char ( #273 )
    Source code(tar.gz)
    Source code(zip)
  • v0.7.4(Jul 6, 2021)

  • v0.7.3(Jun 29, 2021)

  • v0.7.2(Jun 26, 2021)

    Fix decoder

    • Add decoder for func type to fix decoding of nil function value ( #257 )
    • Fix stream decoding of []byte type ( #258 )


    • Improve decoding performance of map[string]interface{} type ( use mapassign_faststr ) ( #256 )
    • Improve encoding performance of empty interface type ( remove recursive calling of vm.Run ) ( #259 )


    • Add bytedance/sonic as benchmark target ( #254 )
    Source code(tar.gz)
    Source code(zip)
  • v0.7.1(Jun 17, 2021)

  • v0.7.0(Jun 12, 2021)

    Support context for MarshalJSON and UnmarshalJSON ( #248 )

    • json.MarshalContext(context.Context, interface{}, ...json.EncodeOption) ([]byte, error)
    • json.NewEncoder(io.Writer).EncodeContext(context.Context, interface{}, ...json.EncodeOption) error
    • json.UnmarshalContext(context.Context, []byte, interface{}, ...json.DecodeOption) error
    • json.NewDecoder(io.Reader).DecodeContext(context.Context, interface{}) error
    type MarshalerContext interface {
      MarshalJSON(context.Context) ([]byte, error)
    type UnmarshalerContext interface {
      UnmarshalJSON(context.Context, []byte) error

    Add DecodeFieldPriorityFirstWin option ( #242 )

    In the default behavior, go-json, like encoding/json, will reflect the result of the last evaluation when a field with the same name exists. I've added new options to allow you to change this behavior. json.DecodeFieldPriorityFirstWin option reflects the result of the first evaluation if a field with the same name exists. This behavior has a performance advantage as it allows the subsequent strings to be skipped if all fields have been evaluated.

    Fix encoder

    • Fix indent number contains recursive type ( #249 )
    • Fix encoding of using empty interface as map key ( #244 )

    Fix decoder

    • Fix decoding fields containing escaped characters ( #237 )


    • Move some tests to subdirectory ( #243 )
    • Refactor package layout for decoder ( #238 )
    Source code(tar.gz)
    Source code(zip)
  • v0.6.1(Jun 2, 2021)

  • v0.6.0(Jun 1, 2021)

    Support Colorize option for encoding (#233)

    b, err := json.MarshalWithOption(v, json.Colorize(json.DefaultColorScheme))
    if err != nil {
    fmt.Println(string(b)) // print colored json



    • Fix opcode layout - Adjust memory layout of the opcode to 128 bytes in a 64-bit environment ( #230 )
    • Refactor encode option ( #231 )
    • Refactor escape string ( #232 )
    Source code(tar.gz)
    Source code(zip)
  • v0.5.1(May 20, 2021)


    • Add type addrShift to enable bigger encoder/decoder cache ( #213 )

    Fix decoder

    • Keep original reference of slice element ( #229 )


    • Refactor Debug mode for encoding ( #226 )
    • Generate VM sources for encoding ( #227 )
    • Refactor validator for null/true/false for decoding ( #221 )
    Source code(tar.gz)
    Source code(zip)
  • v0.5.0(May 8, 2021)

    Supports using omitempty and string tags at the same time ( #216 )

    Fix decoder

    • Fix stream decoder for unicode char ( #215 )
    • Fix decoding of slice element ( #219 )
    • Fix calculating of buffer length for stream decoder ( #220 )


    • replace skipWhiteSpace goto by loop ( #212 )
    Source code(tar.gz)
    Source code(zip)
  • v0.4.14(May 3, 2021)


    • Add valyala/fastjson to benchmark ( #193 )
    • Add benchmark task for CI ( #211 )

    Fix decoder

    • Fix decoding of slice with unmarshal json type ( #198 )
    • Fix decoding of null value for interface type that does not implement Unmarshaler ( #205 )
    • Fix decoding of null value to []byte by json.Unmarshal ( #206 )
    • Fix decoding of backslash char at the end of string ( #207 )
    • Fix stream decoder for null/true/false value ( #208 )
    • Fix stream decoder for slow reader ( #211 )


    • If cap of slice is enough, reuse slice data for compatibility with encoding/json ( #200 )
    Source code(tar.gz)
    Source code(zip)
  • v0.4.13(Apr 20, 2021)

    Fix json.Compact and json.Indent

    • Support validation the input buffer for json.Compact and json.Indent ( #189 )
    • Optimize json.Compact and json.Indent ( improve memory footprint ) ( #190 )
    Source code(tar.gz)
    Source code(zip)
  • v0.4.12(Apr 15, 2021)

    Fix encoder

    • Fix unnecessary indent for empty slice type ( #181 )
    • Fix encoding of omitempty feature for the slice or interface type ( #183 )
    • Fix encoding custom types zero values with omitempty when marshaller exists ( #187 )

    Fix decoder

    • Fix decoder for invalid top level value ( #184 )
    • Fix decoder for invalid number value ( #185 )
    Source code(tar.gz)
    Source code(zip)
  • v0.4.11(Apr 2, 2021)

  • v0.4.10(Apr 2, 2021)

Masaaki Goshima
Masaaki Goshima
Go encoder and decoder for the NetBPM/PNM image formats. Compatible with Go's image packages.

gpnm This package implements an encoder and decoder for PNM image formats. It can be used with Go's image library. It covers all formats as defined by

null 0 Nov 26, 2021
goi - The “Quite OK Image” format encoder / decoder for Go.

goi - The “Quite OK Image” format encoder / decoder for Go. QOI - The “Quite OK Image” - is losslessly image format that offering speedup both compres

neguse 14 Mar 3, 2022
Decoder/Encoder for GhostControls Gate Remotes

ghostcontrols Decoder/Encoder for GhostControls Gate Remotes GhostControls makes a variety of automatic gate operators, transmitters and keypads & rec

null 0 Jan 1, 2022
A high-performance 100% compatible drop-in replacement of "encoding/json"

A high-performance 100% compatible drop-in replacement of "encoding/json" You can also use thrift like JSON using thrift-iterator Benchmark Source cod

Jsoniter 10.8k May 11, 2022
Fast and flexible JSON encoder for Go

Jettison Jettison is a fast and flexible JSON encoder for the Go programming language, inspired by bet365/jingo, with a richer features set, aiming at

William Poussier 126 May 13, 2022
Package json implements encoding and decoding of JSON as defined in RFC 7159

Package json implements encoding and decoding of JSON as defined in RFC 7159. The mapping between JSON and Go values is described in the documentation for the Marshal and Unmarshal functions

High Performance, Kubernetes Native Object Storage 3 May 10, 2022
Fork of Go's standard library json encoder

A fork of the Go standard library's json encoder Why? was proposed in 2013 but was never accepted. Difference 0 Nov 25, 2021
An efficient JSON decoder

pkg/json An alternative JSON decoder for Go. Features pkg/json aims to be a drop in replacement for encoding/json. It features: json.Scanner which, wh

null 285 May 14, 2022
Golang JSON decoder supporting case-sensitive, number-preserving, and strict decoding use cases

Golang JSON decoder supporting case-sensitive, number-preserving, and strict decoding use cases

Kubernetes SIGs 12 Apr 3, 2022
json encoding and decoding

jx Package jx implements encoding and decoding of json [RFC 7159]. Lightweight fork of jsoniter. go get Usage and examples Roa

go faster 53 May 8, 2022
JSON:API compatible query string parser

QParser The package helps to parse part of the URL path and its parameters string to a handy structure. The structure format is compatible with the JS

Velmie 1 Dec 21, 2021
JSON Spanner - A Go package that provides a fast and simple way to filter or transform a json document

JSON SPANNER JSON Spanner is a Go package that provides a fast and simple way to

null 2 May 20, 2022
Fast JSON parser and validator for Go. No custom structs, no code generation, no reflection

fastjson - fast JSON parser and validator for Go Features Fast. As usual, up to 15x faster than the standard encoding/json. See benchmarks. Parses arb

Aliaksandr Valialkin 1.5k May 11, 2022
Fast JSON serializer for golang.

easyjson Package easyjson provides a fast and easy way to marshal/unmarshal Go structs to/from JSON without the use of reflection. In performance test

Free and open source software developed at Mail.Ru 3.7k May 11, 2022
Fast Color JSON Marshaller + Pretty Printer for Golang

ColorJSON: The Fast Color JSON Marshaller for Go What is this? This package is based heavily on hokaccha/go-prettyjson but has some noticible differen

Tyler Brock 107 May 17, 2022
A fast json parser for go

rjson rjson is a json parser that relies on Ragel-generated state machines for most parsing. rjson's api is minimal and focussed on efficient parsing.

WillAbides 49 Feb 23, 2022
A blazingly fast JSON serializing & deserializing library

Sonic A blazingly fast JSON serializing & deserializing library, accelerated by JIT(just-in-time compiling) and SIMD(single-instruction-multi-data). B

Bytedance Inc. 2.8k May 12, 2022
Kazaam was created with the goal of supporting easy and fast transformations of JSON data with Golang

kazaam Description Kazaam was created with the goal of supporting easy and fast transformations of JSON data with Golang. This functionality provides

Qntfy 205 Sep 17, 2021
Fast json for go. Lightweight fork of jsoniter.

jx Fast json for go. Lightweight fork of jsoniter. Features Reduced scope (no reflection or encoding/json adapter) Fuzzing, improved test coverage Dra

ogen 53 May 8, 2022