Häufig gestellte Fragen (FAQ)

JSON-Werkstatt accepts files up to 10 MB on the free plan and up to 50 MB on the Pro plan. Files are parsed entirely in your browser — nothing is uploaded to our servers. If your file exceeds the limit, you'll see a clear error message with a suggestion to split the file or use our streaming API endpoint (POST /api/v2/stream).

Large JSON files (above ~5 MB) can cause noticeable lag because parsing happens on your device's main thread. For files between 5 MB and 10 MB, we recommend using the "Background Parse" toggle in Settings, which offloads parsing to a Web Worker. This keeps the UI responsive while the file is processed. The average parse time for a 10 MB file on a modern laptop is around 1.8 seconds.

Yes. The Batch Mode lets you drop up to 20 JSON files simultaneously. Each file is validated and formatted independently. Batch results are displayed in a summary table with per-file status (valid, invalid, or warning). The combined size of all files in a batch must still respect your plan's limit (10 MB free / 50 MB Pro).

No. All parsing, formatting, validation, and transformation happens entirely client-side in your browser. JSON-Werkstatt never sends your data to any server. The only network requests we make are for loading the application itself and, optionally, fetching remote JSON Schemas you specify. You can verify this by checking your browser's Network tab — no data leaves your machine during normal use.

We use a single essential cookie to remember your preferred output format (pretty-printed or minified) and indentation style. No analytics, no fingerprinting, no third-party trackers. Our privacy policy is available at json-werkstatt.dev/privacy and is written in plain language — no legalese.

Yes. JSON-Werkstatt offers an offline PWA build that you can install once and use without any internet connection. All features — including schema validation against locally stored schemas — work offline. The PWA bundle is approximately 340 KB gzipped.

The free tier allows 1,000 requests per hour and 10,000 requests per day on the REST API (api.json-werkstatt.dev/v2). Rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) are included in every response so you can monitor usage programmatically. When you hit the limit, the API returns 429 Too Many Requests with a Retry-After header.

Pro subscribers get 10,000 requests per hour and 200,000 requests per day. There is no per-IP throttling — limits are tied to your API key. Enterprise customers can negotiate custom limits starting at 1,000,000 requests per day. Contact sales@json-werkstatt.dev for a quote.

Yes, but each streaming session counts as a single request regardless of how long it runs or how much data is transferred. The streaming endpoint (POST /api/v2/stream) is designed for large payloads and uses chunked transfer encoding. Maximum stream duration is 300 seconds; longer streams are gracefully terminated with a 408 Request Timeout.

JSON-Werkstatt validates against JSON Schema Draft 2020-12, Draft 2019-09, Draft-07, and Draft-06. The validator automatically detects the $schema URI in your document. For schemas without a $schema declaration, Draft-07 is used as the default. Custom keywords and meta-schemas can be registered via the API's POST /api/v2/meta-schema endpoint.

JSON-Werkstatt handles JSONL (newline-delimited JSON) and JSON5 out of the box. JSONC (JSON with Comments) is supported via the "Strip Comments" preprocessor toggle. All three formats can be parsed, validated, and converted to standard RFC 8259 JSON. JSON5-specific features like trailing commas, unquoted keys, and hexadecimal numbers are normalized during conversion.

The web app runs on all evergreen browsers: Chrome 110+, Firefox 115+, Safari 16+, and Edge 110+. The PWA requires Service Worker support and works on iOS 16+ and Android 10+. For older browsers, we provide a zero-dependency CLI tool (npm install -g @json-werkstatt/cli) that works on Node.js 18+ and Deno 1.35+.

Yes. All settings — indentation (2 or 4 spaces), sort keys, trim whitespace, schema cache, and custom transformers — can be exported as a single .jsonwerkstatt config file. Import it on another machine or share it with your team. Configs are also available via the API at GET /api/v2/config and PUT /api/v2/config for automated setup in CI/CD pipelines.