TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Go 1.27 includes stable, generally available packages encoding/json/v2 and encoding/json/jsontext, following an experimental release and further refinement. The APIs are designed to address limitations in the longstanding encoding/json package, including permissive handling of invalid UTF-8 and duplicate object names, restricted option handling, and performance constraints. The source does not specify migration details or whether the new packages replace the old API.
The Go team says Go 1.27 includes stable, generally available versions of encoding/json/v2 and encoding/json/jsontext, a new API intended to address longstanding limits in Go’s JSON support. The announcement, published November 4, 2026, follows an experimental release and a period of feedback and refinement; the existing encoding/json package is not stated to be removed.
The new packages are presented as a response to issues reported by users over many years. The Go team says the existing API can accept invalid UTF-8 and JSON objects with duplicate member names, even though these inputs can have ambiguous or unsafe interpretations. The announcement says the new API is intended to favor stricter handling, including rejecting such inputs by default. It also identifies the default encoding of nil slices and maps as JSON null as a compatibility concern for systems expecting arrays or objects.
The announcement also points to API restrictions. Existing encoder and decoder options cannot be applied uniformly through Marshal and Unmarshal calls or reliably passed through custom JSON methods. The team says reading from an io.Reader can be error-prone: a common Decoder usage may fail to reject trailing junk. The existing package’s buffer-oriented helpers and token interface also limit flexibility.
Performance is another stated motivation. The Go team says the existing custom marshaling interfaces can require extra allocations and parsing, while encoder and decoder operations buffer complete JSON values despite using reader and writer interfaces. The announcement introduces the v2 packages as a new design rather than a direct repair to the old API, because the team says some limitations follow from established interfaces and behavior.
Stricter JSON Handling in Go
JSON is widely used to exchange data between services, browsers, and applications, so how a parser treats ambiguous or malformed input can affect compatibility and security. The Go team argues that accepting duplicate names or invalid UTF-8 can produce inconsistent interpretations across systems. A stricter default in a new API could help developers avoid silently accepting input that another component reads differently. The announcement cites past exploitation involving duplicate names, including CVE-2017-12635; that example explains the concern, but does not establish that the new packages prevent every class of JSON-related vulnerability.
For Go developers, the release offers an alternative to the longstanding standard-library API, with the stated goal of improving behavior, option propagation, and performance opportunities. Applications that exchange JSON with other implementations may also benefit from defaults better aligned with common expectations, such as representing nil slices and maps as empty arrays or objects. The practical effect depends on adoption and on how applications configure the new packages.
Popular right now
Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation
LG 55-Inch OLED evo G2 Series 4K Smart TV (OLED55G2PUA, 2022)
De'Longhi Rivelia Fully Automatic Espresso Machine with Milk Frother, White
As an affiliate, we earn on qualifying purchases.
Why Go Added a Separate API
Go has provided JSON support in its standard library since before Go 1.0. The original package, encoding/json, became widely used because it can map arbitrary Go types to JSON and lets developers customize that representation. The Go team says it has held up well overall, but user needs and JSON standardization have exposed behavior and API shortcomings that are difficult to change without breaking existing programs.
The team described an experimental JSON API the previous year. After additional feedback and refinement, the v2 and jsontext packages became stable and generally available in Go 1.27, according to the November 4 announcement. The source describes the packages’ aims and the problems motivating them, but does not give a full compatibility or migration guide in the supplied material.
““After additional feedback and refinement, the new encoding/json/v2 and encoding/json/jsontext packages are stable and generally available in Go 1.27!””
— Michael Pratt, Joe Tsai, Daniel Martí, Johan Brandhorst-Satzkorn, Roger Peppe, Chris Hines and Damien Neil, in the Go blog announcement
Migration and Compatibility Questions
The announcement establishes that the new packages are stable and generally available, but the supplied material does not detail how existing applications should migrate, whether particular defaults differ in every case, or how the new APIs compare across benchmarks. It also does not say that encoding/json will be deprecated or removed. Developers should not assume that upgrading to Go 1.27 automatically changes existing programs to use the v2 packages.
The source describes intended improvements and design motivations, not measured outcomes for every workload. How applications handle stricter rejection of malformed input, duplicate names, or changed nil slice and map representations may depend on their existing data and interoperability requirements.
Adoption After Go 1.27
The packages are available as stable APIs in Go 1.27, so the next step for developers is to review their documentation and evaluate whether they fit new or existing applications. Teams handling external JSON can test how stricter parsing and encoding behavior affects their data flows before switching. The Go announcement does not provide a timetable for further changes to the original encoding/json package, so its future status beyond continued availability remains unspecified in the supplied report.
Key Questions
What did Go announce?
The Go team announced that encoding/json/v2 and encoding/json/jsontext are stable and generally available in Go 1.27.
Do the new packages replace encoding/json?
The announcement does not say that the original encoding/json package is being removed or deprecated. It presents the new packages as a separate API designed to address limitations that are difficult to fix without breaking established behavior.
What problems are the new APIs intended to address?
The Go team cites issues including acceptance of invalid UTF-8 and duplicate JSON object names, limited propagation of options, and performance constraints related to buffering and custom marshaling methods.
Should existing Go applications switch immediately?
The supplied announcement does not prescribe an immediate migration or provide a migration schedule. Developers should check the package documentation and test behavior against their applications’ data and compatibility needs.
Source: go.dev
