String to JSON

How to convert a string to JSON?

Converting plain strings to JSON is essential when working with data from APIs, databases, or legacy systems that return string-formatted values. This tool handles various string formats:

• Enter your string into the input area. The tool accepts several input formats: a quoted string like '"Hello World"' (a JSON-encoded string value), an escaped string like 'He said \"Hello\"\nHow are you?' (raw text with escape sequences), a JSON-like object '{name: John, age: 30}' (JavaScript object notation without quotes), or a JSON array '[1, 2, 3]' (array syntax). The tool detects the input format automatically and applies the appropriate conversion.
• Click 'Convert to JSON' to transform your string into properly formatted JSON. For quoted strings, the tool strips the outer quotes and returns the parsed string value as a JSON string type. For escaped strings, it resolves all escape sequences (\\n → newline, \\\" → quote, \\\\ → backslash) and wraps the result in proper JSON string delimiters. For JavaScript object notation, it converts unquoted keys to quoted keys and produces valid JSON output.
• Review the converted JSON in the output area. The tool displays the result in multiple views: the raw JSON string, a formatted/pretty-printed version with indentation, and a parsed object structure showing types and nesting levels. This multi-view approach helps you verify the conversion produced exactly what you expected.
• Copy the JSON output using the Copy button. Choose which format to copy based on your needs: the raw JSON string for embedding in code, the pretty-printed version for readability, or the parsed structure for inspection. Paste the result into your application, API request body, configuration file, or database insert statement.

Understanding string-to-JSON conversion scenarios

The need to convert strings to JSON arises in several common development scenarios. When reading data from localStorage or sessionStorage, all values are stored as strings — even if you originally saved an object. Calling JSON.parse(localStorage.getItem('user')) converts the stored string back to an object. API responses sometimes return JSON-wrapped strings instead of native JSON objects, particularly in older REST APIs or when data passes through middleware that serializes responses. Database exports often produce CSV or string-formatted data that needs JSON conversion for modern frontend consumption. Legacy systems and SOAP web services frequently return XML or string-based responses rather than native JSON. Configuration files in non-standard formats (INI, properties files, environment variable strings) need conversion to JSON for use with JSON-based configuration systems. When building data pipelines, ETL processes often receive string-formatted records that must be parsed into structured JSON before loading into data warehouses or analytics platforms. Understanding these scenarios helps you recognize when string-to-JSON conversion is needed and choose the right approach for each case.

Common pitfalls when converting strings to JSON

String-to-JSON conversion seems straightforward but harbors several subtle traps. Single quotes vs double quotes is the most common issue: JSON strictly requires double quotes for strings and property names, but many string inputs use single quotes ('value' instead of "value"). A naive parser will reject single-quoted JSON, while a robust converter attempts to normalize them first. Trailing commas in object literals ({key: 'value',}) are valid JavaScript but illegal in JSON — they cause parse errors. Unicode escape sequences (\uXXXX) must be correctly interpreted; malformed unicode escapes like \uXYZW produce errors. Nested escaping creates confusion: a string containing literal backslashes ('C:\\path\\to\\file') requires careful handling to distinguish between escape sequences and literal characters. Double-wrapped JSON ('{"key":"value"}' inside another set of quotes) requires two parse operations. Empty strings ('') versus null versus undefined represent different JSON types and require different handling. Date strings ('2024-01-15') become plain strings after JSON parsing, not Date objects — you need a reviver function to restore date semantics. Numbers represented as strings ('42' vs 42) have different JSON types and may cause type mismatches in downstream code. Always validate your input format before attempting conversion, and wrap parse operations in try-catch blocks to handle unexpected formats gracefully.