Svelte Jsoneditor

A web-based tool to view, edit, format, repair, query, transform, and validate JSON
Alternatives To Svelte Jsoneditor
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Editor.js25,001372662 days ago84November 08, 2023556apache-2.0TypeScript
A block-style editor with clean JSON output
Jsoneditor10,68338339920 days ago203November 08, 2023222apache-2.0JavaScript
A web-based tool to view, edit, format, and validate JSON
Json Editor5,376141366 years ago19August 07, 2016461mitJavaScript
JSON Schema Based Editor
Json Editor3,9911121a day ago41November 16, 2023205mitJavaScript
JSON Schema Based Editor
Kityminder Editor2,96723 months ago11February 14, 2019640gpl-2.0JavaScript
Powerful Mindmap Editing Tool
Json Splora1,76627 years ago11December 13, 201618mitJavaScript
GUI for editing, visualizing, and manipulating JSON data
a month agomitJavaScript
CrossUI is a free Cross-Browser Javascript framework with cutting-edge functionality for rich web application
Svelte Jsoneditor6221004 days ago76November 21, 202341otherTypeScript
A web-based tool to view, edit, format, repair, query, transform, and validate JSON
Jsonedit54625 years ago1June 03, 20209mitJavaScript
User friendly, visual JSON editor built as an Angular 1 directive.
Flexijsoneditor53425 years ago5May 21, 201818otherJavaScript
JSON editor jQuery plugin
Alternatives To Svelte Jsoneditor
Select To Compare

Alternative Project Comparisons


A web-based tool to view, edit, format, transform, and validate JSON.

Try it out:

The library is written with Svelte, but can be used in plain JavaScript too and in any framework (SolidJS, React, Vue, Angular, etc).

JSONEditor tree mode screenshot JSONEditor text mode screenshot JSONEditor table mode screenshot


  • View and edit JSON
  • Has a low level text editor and high level tree view and table view
  • Format (beautify) and compact JSON
  • Sort, query, filter, and transform JSON
  • Repair JSON
  • JSON schema validation and pluggable custom validation
  • Color highlighting, undo/redo, search and replace
  • Utilities like a color picker and timestamp tag
  • Handles large JSON documents up to 512 MB


For usage in a Svelte project:

npm install svelte-jsoneditor

For usage in vanilla JavaScript or frameworks like SolidJS, React, Vue, Angular, etc:

npm install vanilla-jsoneditor



Svelte usage

Create a JSONEditor with two-way binding bind:json:

  import { JSONEditor } from 'svelte-jsoneditor'

  let content = {
    text: undefined, // can be used to pass a stringified JSON document instead
    json: {
      array: [1, 2, 3],
      boolean: true,
      color: '#82b92c',
      null: null,
      number: 123,
      object: { a: 'b', c: 'd' },
      string: 'Hello World'

  <JSONEditor bind:content />

Or one-way binding:

  import { JSONEditor } from 'svelte-jsoneditor'

  let content = {
    text: undefined, // can be used to pass a stringified JSON document instead
    json: {
      greeting: 'Hello World'

  function handleChange(updatedContent, previousContent, { contentErrors, patchResult }) {
    // content is an object { json: JSONValue } | { text: string }
    console.log('onChange: ', { updatedContent, previousContent, contentErrors, patchResult })
    content = updatedContent

  <JSONEditor {content} onChange="{handleChange}" />

Standalone bundle (use in React, Vue, Angular, plain JavaScript, ...)

The library provides a standalone bundle of the editor via the npm library vanilla-jsoneditor (instead of svelte-jsoneditor) which can be used in any browser environment and framework. In a framework like React, Vue, or Angular, you'll need to write some wrapper code around the class interface.

Note that the vanilla-jsoneditor package contains all dependencies. These are purely needed for the TypeScript types that they export.

Browser example loading the ES module:

<!doctype html>
<html lang="en">
    <div id="jsoneditor"></div>

    <script type="module">
      import { JSONEditor } from 'vanilla-jsoneditor'

      // Or use it through a CDN (not recommended for use in production):
      // import { JSONEditor } from ''
      // import { JSONEditor } from ''

      let content = {
        text: undefined,
        json: {
          greeting: 'Hello World'

      const editor = new JSONEditor({
        target: document.getElementById('jsoneditor'),
        props: {
          onChange: (updatedContent, previousContent, { contentErrors, patchResult }) => {
            // content is an object { json: JSONValue } | { text: string }
            console.log('onChange', { updatedContent, previousContent, contentErrors, patchResult })
            content = updatedContent

      // use methods get, set, update, and onChange to get data in or out of the editor.
      // Use updateProps to update properties.

Wrapper libraries for specific frameworks

To make it easier to use the library in your framework of choice, you can use a wrapper library:



Svelte component:

  import { JSONEditor } from 'svelte-jsoneditor'

  let content = { text: '[1,2,3]' }

  <JSONEditor {content} />

JavasScript class:

import { JSONEditor } from 'vanilla-jsoneditor'

const content = { text: '[1,2,3]' }

const editor = new JSONEditor({
  target: document.getElementById('jsoneditor'),
  props: {
    onChange: (updatedContent, previousContent, { contentErrors, patchResult }) => {
      // content is an object { json: JSONValue } | { text: string }
      console.log('onChange', { updatedContent, previousContent, contentErrors, patchResult })


  • content: Content Pass the JSON contents to be rendered in the JSONEditor. Content is an object containing a property json (a parsed JSON document) or text (a stringified JSON document). Only one of the two properties must be defined. You can pass both content types to the editor independent of in what mode it is. You can use two-way binding via bind:content.

  • selection: JSONEditorSelection | null The current selected contents. You can use two-way binding using bind:selection. The tree mode supports MultiSelection, KeySelection, ValueSelection, InsideSelection, or AfterSelection. The table mode supports ValueSelection, and text mode supports TextSelection..

  • mode: 'tree' | 'text' | 'table'. Open the editor in 'tree' mode (default), 'table' mode, or 'text' mode (formerly: code mode).

  • mainMenuBar: boolean Show the main menu bar. Default value is true.

  • navigationBar: boolean Show the navigation bar with, where you can see the selected path and navigate through your document from there. Default value is true.

  • statusBar: boolean Show a status bar at the bottom of the 'text' editor, showing information about the cursor location and selected contents. Default value is true.

  • askToFormat: boolean When true (default), the user will be asked whether he/she wants to format the JSON document when a compact document is loaded or pasted in 'text' mode. Only applicable to 'text' mode.

  • readOnly: boolean Open the editor in read-only mode: no changes can be made, non-relevant buttons are hidden from the menu, and the context menu is not enabled. Default value is false.

  • indentation: number | string Number of spaces use for indentation when stringifying JSON, or a string to be used as indentation like '\t' to use a tab as indentation, or ' ' to use 4 spaces (which is equivalent to configuring indentation: 4). See also property tabSize.

  • tabSize: number When indentation is configured as a tab character (indentation: '\t'), tabSize configures how large a tab character is rendered. Default value is 4. Only applicable to text mode.

  • escapeControlCharacters: boolean. False by default. When true, control characters like newline and tab are rendered as escaped characters \n and \t. Only applicable for 'tree' mode, in 'text' mode control characters are always escaped.

  • escapeUnicodeCharacters: boolean. False by default. When true, unicode characters like and are rendered escaped like \u260e and \ud83d\ude00.

  • flattenColumns: boolean. True by default. Only applicable to 'table' mode. When true, nested object properties will be displayed each in their own column, with the nested path as column name. When false, nested objects will be rendered inline, and double-clicking them will open them in a popup.

  • validator: function (json: JSONValue): ValidationError[]. Validate the JSON document. For example use the built-in JSON Schema validator powered by Ajv:

    import { createAjvValidator } from 'svelte-jsoneditor'
    const validator = createAjvValidator({ schema, schemaDefinitions })
  • parser: JSON = JSON. Configure a custom JSON parser, like lossless-json. By default, the native JSON parser of JavaScript is used. The JSON interface is an object with a parse and stringify function. For example:

      import { JSONEditor } from 'svelte-jsoneditor'
      import { parse, stringify } from 'lossless-json'
      const LosslessJSONParser = { parse, stringify }
      let content = { text: '[1,2,3]' }
      <JSONEditor {content} parser="{LosslessJSONParser}" />
  • validationParser: JSONParser = JSON. Only applicable when a validator is provided. This is the same as parser, except that this parser is used to parse the data before sending it to the validator. Configure a custom JSON parser that is used to parse JSON before passing it to the validator. By default, the built-in JSON parser is used. When passing a custom validationParser, make sure the output of the parser is supported by the configured validator. So, when the validationParser can output bigint numbers or other numeric types, the validator must also support that. In tree mode, when parser is not equal to validationParser, the JSON document will be converted before it is passed to the validator via validationParser.parse(parser.stringify(json)).

  • pathParser: JSONPathParser. An optional object with a parse and stringify method to parse and stringify a JSONPath, which is an array with property names. The pathParser is used in the path editor in the navigation bar, which is opened by clicking the edit button on the right side of the navigation bar. The pathParser.parse function is allowed to throw an Error when the input is invalid. By default, a JSON Path notation is used, which looks like $.data[2] Alternatively, it is possible to use for example a JSON Pointer notation like /data/2/nested/property or something custom-made. Related helper functions: parseJSONPath and stringifyJSONPath, parseJSONPointer and compileJSONPointer.

  • onError(err: Error). Callback fired when an error occurs. Default implementation is to log an error in the console and show a simple alert message to the user.

  • onChange(content: Content, previousContent: Content, changeStatus: { contentErrors: ContentErrors | null, patchResult: JSONPatchResult | null }). The callback which is invoked on every change of the contents, both changes made by a user and programmatic changes made via methods like .set(), .update(), or .patch(). The returned content is sometimes of type { json }, and sometimes of type { text }. Which of the two is returned depends on the mode of the editor, the change that is applied, and the state of the document (valid, invalid, empty). Please be aware that { text } can contain invalid JSON: whilst typing in text mode, a JSON document will be temporarily invalid, like when the user is typing a new string. The parameter patchResult is only returned on changes that can be represented as a JSON Patch document, and for example not when freely typing in text mode.

  • onChangeMode(mode: 'tree' | 'text' | 'table'). Invoked when the mode is changed.

  • onClassName(path: Path, value: any): string | undefined. Add a custom class name to specific nodes, based on their path and/or value. Note that in the custom class, you can override CSS variables like --jse-contents-background-color to change the styling of a node, like the background color. Relevant variables are:


    To adjust the text color of keys or values, the color of the classes .jse-key and .jse-value can be overwritten.

  • onRenderValue(props: RenderValueProps) : RenderValueComponentDescription[]

    EXPERIMENTAL! This API will most likely change in future versions.

    Customize rendering of the values. By default, renderValue is used, which renders a value as an editable div and depending on the value can also render a boolean toggle, a color picker, and a timestamp tag. Multiple components can be rendered alongside each other, like the boolean toggle and color picker being rendered left from the editable div. Built in value renderer components: EditableValue, ReadonlyValue, BooleanToggle, ColorPicker, TimestampTag, EnumValue.

    For JSON Schema enums, there is a value renderer renderJSONSchemaEnum which renders enums using the EnumValue component. This can be used like:

    import { renderJSONSchemaEnum, renderValue } from 'svelte-jsoneditor'
    function onRenderValue(props) {
      // use the enum renderer, and fallback on the default renderer
      return renderJSONSchemaEnum(props, schema, schemaDefinitions) || renderValue(props)
  • onRenderMenu(items: MenuItem[], context: { mode: 'tree' | 'text' | 'table', modal: boolean }) : MenuItem[] | undefined. Callback which can be used to make changes to the menu items. New items can be added, or existing items can be removed or reorganized. When the function returns undefined, the original items will be applied. Using the context values mode and modal, different actions can be taken depending on the mode of the editor and whether the editor is rendered inside a modal or not.

    A menu item MenuItem can be one of the following types:

    • Button:

      interface MenuButtonItem {
        onClick: () => void
        icon?: IconDefinition
        text?: string
        title?: string
        className?: string
        disabled?: boolean
    • Separator (gray vertical line between a group of items):

      interface MenuSeparatorItem {
        separator: true
    • Space (fills up empty space):

      interface MenuSpaceItem {
        space: true
  • onSelect: (selection: JSONEditorSelection | null) => void

    Callback invoked when the selection is changed. When the selection is removed, the callback is invoked with undefined as argument. In text mode, a TextSelection will be fired. In tree and table mode, a JSONSelection will be fired (which can be MultiSelection, KeySelection, ValueSelection, InsideSelection, or AfterSelection). Use typeguards like isTextSelection and isValueSelection to check what type the selection has.

  • queryLanguages: QueryLanguage[].
    Configure one or multiple query language that can be used in the Transform modal. The library comes with three languages:

    import {
    } from 'svelte-jsoneditor'
    const allQueryLanguages = [jmespathQueryLanguage, lodashQueryLanguage, javascriptQueryLanguage]

    By default, only javascriptQueryLanguage is loaded.

  • queryLanguageId. The id of the currently selected query language.

  • onChangeQueryLanguage: (queryLanguageId: string) => void. Callback function invoked when the user changes the selected query language in the TransformModal via the configuration button top right.

  • onFocus() callback fired when the editor got focus.

  • onBlur() callback fired when the editor lost focus.


Note that most methods are asynchronous and will resolve after the editor is re-rendered (on the next tick).

  • get(): Content Get the current JSON document.

  • set(content: Content): Promise<void> Replace the current content. Will reset the state of the editor. See also method update(content).

  • update(content: Content): Promise<void> Update the loaded content, keeping the state of the editor (like expanded objects). You can also call editor.updateProps({ content }). See also method set(content).

  • patch(operations: JSONPatchDocument) : Promise<JSONPatchResult> Apply a JSON patch document to update the contents of the JSON document. A JSON patch document is a list with JSON Patch operations.

  • updateProps(props: Object): Promise<void> update some or all of the properties. Updated content can be passed too; this is equivalent to calling update(content). Example:

      readOnly: true
  • expand([callback: (path: Path) => boolean]): Promise<void> Expand or collapse paths in the editor. The callback determines which paths will be expanded. If no callback is provided, all paths will be expanded. It is only possible to expand a path when all of its parent paths are expanded too. Examples:

    • editor.expand(path => true) expand all
    • editor.expand(path => false) collapse all
    • editor.expand(path => path.length < 2) expand all paths up to 2 levels deep
  • transform({ id?: string, rootPath?: [], onTransform: ({ operations: JSONPatchDocument, json: JSONValue, transformedJson: JSONValue }) => void, onClose: () => void }) programmatically trigger clicking of the transform button in the main menu, opening the transform model. If a callback onTransform is provided, it will replace the build-in logic to apply a transform, allowing you to process the transform operations in an alternative way. If provided, onClose callback will trigger when the transform modal closes, both after the user clicked apply or cancel. If an id is provided, the transform modal will load the previous status of this id instead of the status of the editors transform modal.

  • scrollTo(path: Path): Promise<void> Scroll the editor vertically such that the specified path comes into view. Only applicable to modes tree and table. The path will be expanded when needed. The returned Promise is resolved after scrolling is finished.

  • findElement(path: Path) Find the DOM element of a given path. Returns null when not found.

  • acceptAutoRepair(): Promise<Content> In tree mode, invalid JSON is automatically repaired when loaded. When the repair was successful, the repaired contents are rendered but not yet applied to the document itself until the user clicks "Ok" or starts editing the data. Instead of accepting the repair, the user can also click "Repair manually instead". Invoking .acceptAutoRepair() will programmatically accept the repair. This will trigger an update, and the method itself also returns the updated contents. In case of text mode or when the editor is not in an "accept auto repair" status, nothing will happen, and the contents will be returned as is.

  • refresh(): Promise<void>. Refresh rendering of the contents, for example after changing the font size. This is only available in text mode.

  • validate() : ContentErrors | null. Get all current parse errors and validation errors.

  • select(newSelection: JSONEditorSelection | null) change the current selection. See also option selection.

  • focus(): Promise<void>. Give the editor focus.

  • destroy(): Promise<void>. Destroy the editor, remove it from the DOM.

Utility functions

  • Rendering of values:
    • renderValue
    • renderJSONSchemaEnum
    • Components:
      • BooleanToggle
      • ColorPicker
      • EditableValue
      • EnumValue
      • ReadonlyValue
      • TimestampTag
  • Validation:
    • createAjvValidator
  • Query languages:
    • lodashQueryLanguage
    • javascriptQueryLanguage
    • jmespathQueryLanguage
  • Content:
    • isContent
    • isTextContent
    • isJSONContent
    • isLargeContent
    • toTextContent
    • toJSONContent
    • estimateSerializedSize
  • Selection:
    • isValueSelection
    • isKeySelection
    • isInsideSelection
    • isAfterSelection
    • isMultiSelection,
    • isEditingSelection
    • createValueSelection
    • createKeySelection
    • createInsideSelection,
    • createAfterSelection
    • createMultiSelection
  • Parser:
    • isEqualParser
  • Path:
    • parseJSONPath
    • stringifyJSONPath
  • Actions:
    • resizeObserver
    • onEscape
  • Typeguards:
    • isContentParseError
    • isContentValidationErrors
  • More: you can install immutable-json-patch and use its functions:
    • immutableJSONPatch
    • revertJSONPatch
    • parseJSONPointer
    • parsePath
    • parseFrom
    • compileJSONPointer
    • compileJSONPointerProp
    • getIn
    • setIn
    • updateIn
    • insertAt
    • existsIn
    • deleteIn


The TypeScript types (like Content, JSONSelection, and JSONPatchOperation) are defined in the following source file:


The editor can be styled using the available CSS variables. A full list with all variables can be found here:

Custom theme color

For example, to change the default blue theme color to anthracite:

  import { JSONEditor } from 'svelte-jsoneditor'

  let content = {
    text: undefined, // can be used to pass a stringified JSON document instead
    json: {
      string: 'Hello custom theme color :)'

<div class="my-json-editor">
  <JSONEditor bind:content />

  .my-json-editor {
    /* define a custom theme color */
    --jse-theme-color: #383e42;
    --jse-theme-color-highlight: #687177;

Dark theme

The editor comes with a built-in dark theme. To use this theme:

  • Load the css file of the dark theme: themes/jse-theme-dark.css
  • Add the class name jse-theme-dark of the dark theme to the HTML container element where the editor is loaded.

It is possible to load styling of multiple themes, and toggle them by changing the class name (like jse-theme-dark) attached to the HTML container element.

Full Svelte example:

  import { JSONEditor } from 'svelte-jsoneditor'

  let content = {
    text: undefined, // can be used to pass a stringified JSON document instead
    json: {
      string: 'Hello dark theme :)'

<!-- use a theme by adding its name to the container class -->
<div class="my-json-editor jse-theme-dark">
  <JSONEditor bind:content />

  /* load one or multiple themes */
  @import 'svelte-jsoneditor/themes/jse-theme-dark.css';

Updating styles dynamically

When updating CSS variables dynamically, it is necessary to refresh the via editorRef.refresh() to update the font-size of the line numbers in the gutter and update the colors of the indentation markers in text mode:

  let editorRef

  function refresh() {
<JSONEditor bind:this="{editorRef}" ... />

Differences between josdejong/svelte-jsoneditor and josdejong/jsoneditor

This library josdejong/svelte-jsoneditor is the successor of josdejong/jsoneditor. The main differences are:

josdejong/jsoneditor josdejong/svelte-jsoneditor
Creation Original (first published in 2011) Successor (first published in 2021)
Framework Implemented in plain JavaScript, using low level DOM operations Uses Svelte
Tree mode A tree view having context menu buttons on the left of every line. The keys and values are always in editable state. A tree view utilizing right-click to open the context menu, and double-click to start editing a key or value (more similar to a Spreadsheet or text editor). It supports copy/paste from and to the system clipboard.
Text mode Powered by Ace editor Powered by Code Mirror
Preview mode Used to preview large documents Not needed, both tree and text mode can handle large documents

The main reasons to create a new library instead of extending the existing one are:

  • The codebase had become hard to maintain, the architecture needed a big overhaul. The codebase uses plain JavaScript to create and update the DOM based on changes in the state of the application. This is complex. Letting a framework like Svelte do this for you makes the code base much simpler.
  • Performance limitations in the old editor.
  • Tree mode: the classic tree mode of josdejong/jsoneditor is simple and straightforward, but also limited. The new tree mode of josdejong/svelte-jsoneditor allows for much more streamlined editing and interaction. It works quite similar to a Spreadsheet or text editor. Navigate and select using the Arrow and Shift+Arrow keys or by dragging with the mouse. Double-click (or press Enter) to start editing a key or value. Open the context menu by right-clicking on the item or selection you want to operate on. Use cut/copy/paste to move parts of the JSON around and interoperate with other applications.
  • Code or text mode: the Ace editor library is using an outdated module system (AMD) and the way it is bundled and published is hard to integrate in modern JavaScript projects. Code Mirror 6 is very straightforward to integrate, has much better performance, and is very extensible (paving the way for future features).

Known issues

When the library gives compile errors in your Svelte setup, it could be related to Vite having trouble importing ESM/CommonJS libraries the right way. The error could look like:

SyntaxError: The requested module '/node_modules/json-source-map/index.js?v=fda884be' does not provide an export named 'default' (at jsonUtils.js?v=fda884be:2:8)

A workaround is to add the following to your vite.config.js file (read more):

// ...

/** @type {import('vite').UserConfig} */
const config = {
  // ...
  optimizeDeps: {
    include: [

// ...


Clone the git repository

Install dependencies (once):

npm install

Start the demo project (at http://localhost:5173):

npm run dev

Build the library:

npm run build

Run unit tests (in watch mode):

npm test

Run unit tests and exit:

npm run test-ci

Run linter:

npm run lint

Run coverage (coverage results will be generated in the folder ./coverage):

npm run coverage

Automatically fix linting issues:

npm run format

Publish to npm (will increase version number and publish to npm):

npm run release

Note that it will publish two npm packages: svelte-jsoneditor and vanilla-jsoneditor. You'll need to enter a one-time password for npm.

To try a build and see the change list, run:

npm run release-dry-run


svelte-jsoneditor is released as open source under the permissive the ISC license.

If you are using svelte-jsoneditor commercially, there is a social (but no legal) expectation that you help fund its maintenance. Start here.

Popular Json Projects
Popular Editor Projects
Popular Data Formats Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.