Skip to main content

Provides high-performance and low-allocating types that serialize objects to JavaScript Object Notation (JSON) text and deserialize JSON text to objects, with UTF-8 support built-in. Also provides types to read and write JSON text encoded as UTF-8, and to create an in-memory document object model (DOM), that is read-only, for random access of the JSON elements within a structured view of the data. The System.Text.Json library is built-in as part of the shared framework in .NET Runtime. The package can be installed when you need to use it in other target frameworks.

Total Downloads
6.1B
6,090,336,417
Published
May 12, 2026
Latest stable version

Install

.NET CLI
dotnet add package System.Text.Json --version 11.0.0-preview.4.26230.115
Package Manager Console
Install-Package System.Text.Json -Version 11.0.0-preview.4.26230.115
PackageReference
<PackageReference Include="System.Text.Json" Version="11.0.0-preview.4.26230.115" />

Frameworks

net10.0 net11.0 .NETFramework4.6.2 .NETStandard2.0

Dependencies

[11.0.0-preview.4.26230.115, )
[11.0.0-preview.4.26230.115, )
[11.0.0-preview.4.26230.115, )
System.IO.Pipelines
.NETFramework4.6.2
[11.0.0-preview.4.26230.115, )
System.Text.Encodings.Web
.NETFramework4.6.2
[11.0.0-preview.4.26230.115, )
System.Buffers
.NETFramework4.6.2
[4.6.1, )
System.Memory
.NETFramework4.6.2
[4.6.3, )
[6.1.2, )
[4.6.3, )
System.ValueTuple
.NETFramework4.6.2
[4.6.2, )
[11.0.0-preview.4.26230.115, )
System.IO.Pipelines
.NETStandard2.0
[11.0.0-preview.4.26230.115, )
[11.0.0-preview.4.26230.115, )
System.Buffers
.NETStandard2.0
[4.6.1, )
System.Memory
.NETStandard2.0
[4.6.3, )
[4.6.3, )

Adoption guide

New .NET applications that target modern runtimes and can use its supported serializer model.

JSON guide
Why it appears in the guide: The JSON stack built into modern .NET, with source generation and a low-allocation design. Trade-off: Check behavior differences before migrating Newtonsoft.Json attributes, converters or reference handling.

This version is marked prerelease. Validate its API and upgrade path before production use.

Compatibility metadata lists 4 target frameworks; confirm the exact target used by your application.

The published metadata declares 17 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.