w

Frequently Asked Questions

This section addresses common questions and issues users encounter when using the JSON Diff Tool.

General Usage

Q: What is the maximum size of JSON objects I can compare?

A: The tool can handle JSON objects up to 1MB efficiently. For larger objects, performance may be affected, and we recommend breaking them into smaller parts for better results.

Q: Does the tool work offline?

A: Yes, the JSON Diff Tool works completely offline. All processing is done locally in your browser, and no data is sent to external servers.

Q: Can I compare more than two JSON objects at once?

A: Currently, the tool compares two JSON objects at a time. For comparing multiple objects, you can perform multiple comparisons and use the history feature to track them.

Q: What browsers are supported?

A: The tool works in all modern browsers including Chrome 60+, Firefox 55+, Safari 12+, and Edge 79+.

JSON Validation

Q: Why is my JSON showing as invalid?

A: Common causes include:

  • Missing quotes around property names
  • Trailing commas after the last item
  • Unclosed brackets or braces
  • Invalid escape sequences in strings

Use the "Format" button to automatically fix common formatting issues.

Q: Can I compare invalid JSON objects?

A: No, both JSON objects must be valid for comparison to work. The tool will show validation errors and highlight problematic areas.

Q: Does the tool support JSON with comments?

A: No, the tool follows strict JSON specification and doesn't support comments. Remove any comments before comparison.

Comparison Results

Q: Why are identical JSON objects showing differences?

A: This can happen due to:

  • Different formatting (spaces, indentation)
  • Different property order
  • Different number representations (1 vs 1.0)
  • Different string quotes (single vs double)

The tool performs strict value comparison, so formatting differences are ignored.

Q: How does the tool handle array order?

A: The tool compares arrays element by element in order. If array elements are in different positions, they will be marked as modified or moved.

Q: What's the difference between "modified" and "type changed"?

A:

  • Modified: Same data type, different value (e.g., "hello" → "world")
  • Type Changed: Different data type (e.g., "123" → 123, or "true" → true)

History Management

Q: How many history records can I save?

A: The tool saves up to 50 comparison records. When you exceed this limit, the oldest records are automatically removed.

Q: Where is my history stored?

A: History is stored locally in your browser's local storage. It persists across browser sessions but is specific to each browser and device.

Q: Can I export my history?

A: Currently, history export is not available. You can manually copy important comparisons or use the browser's developer tools to access local storage data.

Q: Why is my history not saving?

A: Possible reasons:

  • Browser is in private/incognito mode
  • Local storage is disabled
  • Browser storage quota is exceeded
  • One or both JSON inputs are invalid

Q: Can I share my history between devices?

A: No, history is stored locally on each device. There's no cloud sync functionality to protect your privacy.

Performance

Q: Why is the comparison slow for large JSON objects?

A: Large objects require more processing time. Consider:

  • Breaking large objects into smaller parts
  • Closing other browser tabs to free memory
  • Using a more powerful device for very large files

Q: Can I compare JSON files directly?

A: The tool works with JSON text input. To compare files, copy and paste their contents into the input areas.

Q: Does the tool handle circular references?

A: No, JSON with circular references cannot be parsed and will show as invalid. Remove circular references before comparison.

Data Privacy

Q: Is my JSON data sent to any servers?

A: No, all processing happens locally in your browser. Your data never leaves your device.

Q: Can I use this tool with sensitive data?

A: Yes, the tool is safe for sensitive data since everything is processed locally. However, be cautious about browser history and cache.

Q: How can I ensure complete privacy?

A: For maximum privacy:

  • Use private/incognito browsing mode
  • Clear browser history and cache after use
  • Don't save comparisons to history for sensitive data

Troubleshooting

Q: The tool is not displaying any differences. What's wrong?

A: Check:

  • Both JSON inputs are valid (green validation badges)
  • JSON objects are actually different
  • Input areas are not empty
  • Browser console for any error messages

Q: Copy function is not working. How can I fix it?

A: Try:

  • Check browser permissions for clipboard access
  • Use keyboard shortcuts (Ctrl/Cmd + C)
  • Ensure the text is not too long
  • Try a different browser

Q: The tree view is not expanding. What should I do?

A: This might be due to:

  • Very large JSON objects (try smaller objects first)
  • Browser performance issues (close other tabs)
  • JavaScript errors (check browser console)

Q: Why are some changes not highlighted correctly?

A: This can happen with:

  • Complex nested structures
  • Very large objects
  • Browser rendering issues

Try refreshing the page or using a different browser.

Advanced Features

Q: Can I customize the color scheme for differences?

A: Currently, the color scheme is fixed. Future versions may include customization options.

Q: Is there an API for programmatic access?

A: The tool runs in the browser, but you can access comparison functions through the browser console for programmatic use.

Q: Can I integrate this tool into my development workflow?

A: Yes, you can:

  • Use it for API testing and validation
  • Compare configuration files
  • Validate data transformations
  • Integrate with browser automation tools

Q: Does the tool support different JSON schemas?

A: The tool compares JSON values regardless of schema. It doesn't validate against specific schemas but can help identify structural changes.

Browser-Specific Issues

Q: The tool doesn't work in Internet Explorer. Why?

A: The tool uses modern JavaScript features not supported in Internet Explorer. Use a modern browser like Chrome, Firefox, Safari, or Edge.

Q: Performance is poor in Safari. What can I do?

A: Safari may have different performance characteristics. Try:

  • Updating to the latest Safari version
  • Closing other tabs and applications
  • Using a different browser for large comparisons

Q: The tool looks different in Firefox. Is this normal?

A: Minor visual differences between browsers are normal due to different rendering engines. The functionality remains the same.

Data Formats

Q: Can I compare JSON with other formats like XML or YAML?

A: No, the tool only compares JSON objects. Convert other formats to JSON first using appropriate conversion tools.

Q: Does the tool preserve data types accurately?

A: Yes, the tool maintains strict type checking and will show type changes (e.g., string "123" vs number 123).

Q: How does the tool handle special characters in JSON?

A: The tool handles all valid JSON characters including Unicode, escape sequences, and special characters according to JSON specification.

Getting Help

Q: Where can I report bugs or request features?

A: You can report issues through the tool's feedback system or contact the development team through the main website.

Q: Is there documentation for developers?

A: Yes, technical documentation is available for developers who want to integrate or extend the tool's functionality.

Q: Can I contribute to the tool's development?

A: The tool is open to contributions. Check the project repository for contribution guidelines and development setup instructions.

Best Practices

Q: What's the best way to compare large JSON objects?

A:

  • Break them into logical sections
  • Compare related parts separately
  • Use the history feature to track multiple comparisons
  • Consider using a more powerful device for very large files

Q: How can I make the most of the history feature?

A:

  • Save important comparisons with descriptive titles
  • Regularly clean up old history entries
  • Use history to track changes over time
  • Load from history to continue previous work

Q: What should I do if I find a bug?

A:

  • Note the exact steps to reproduce the issue
  • Check the browser console for error messages
  • Try the same comparison in a different browser
  • Report the issue with as much detail as possible

This FAQ covers the most common questions about the JSON Diff Tool. If you have additional questions not covered here, please refer to the other documentation sections or contact support.

Was this page helpful?