ここで扱うファイルはすべて、あなたの端末に残ります。
PDF、画像、開発者、SEO、テキスト、学生、ビジネス向けツール — すべて無料、すべてブラウザ内で完結。アップロードなし、アカウントなし、サーバーがデータを見ることはありません。
Popular tools
The highest-demand tools with full options — browse by category below for the rest.
How this actually works
Each tool runs entirely with JavaScript already loaded in this page — PDF tools via pdf-lib and pdf.js, image tools via the browser's native Canvas API, and everything else with plain JavaScript. Your files or input are read into browser memory, processed, and handed back as a download or copyable result. This page itself is served by a small Laravel route; Laravel never sees your files either. The only backend in use is Supabase, and only for two optional things: signing in with a magic link, and — only if you're signed in — a log of which tool you ran and when. Honest limits worth knowing: Compress PDF flattens each page to a re-encoded image (great for scans, not ideal if you need selectable text after); HEIC conversion depends on your browser (Safari usually works; Chrome often cannot decode HEIC without a library we don't ship); Fill PDF Form is best-effort for simple AcroForm fields, not a full Adobe Forms replacement; and Word/Excel/PowerPoint ⇄ PDF genuinely needs a server-side engine, so it isn't included — this build only ships tools that can honestly run client-side.
Questions people actually ask
Can it minify JSON as well as format it?
Yes — toggle to Minify to collapse it to a single compact line instead of pretty-printing it.
What happens if my JSON has a syntax error?
You'll get the browser's own parser error message, including the position of the problem, instead of a blank or broken result.
Can I choose the indent size?
Yes — 2 spaces, 4 spaces, or a tab character, selectable when in Pretty-print mode.
Does it validate JSON, or just format it?
Both — it must successfully parse as valid JSON before it can be formatted or minified at all, so a successful result also confirms the JSON is valid.
Does it reorder object keys?
No — key order from the input is preserved exactly, since JSON.parse/JSON.stringify keep insertion order for object keys.
Can I format deeply nested JSON?
Yes — there's no depth limit beyond what your browser can parse and hold in memory.
Does minifying remove whitespace inside string values?
No — only structural whitespace (indentation, line breaks between elements) is removed; the actual content of string values is untouched.
Is my JSON sent anywhere?
No — parsing and formatting happen entirely in your browser using the built-in JSON object.
Is this really free, and is there a file size limit?
Yes — no account, no paywall. Since processing happens in your browser's memory rather than uploading anywhere, the practical limit is your device's available RAM, not a server quota. Very large files (500+ pages) may run slower, especially for Compress and PDF→JPG.
Does anything about my file get sent anywhere?
No. Every tool runs with pdf-lib/pdf.js loaded in this page; your file is read into browser memory and never leaves it. The only network call this app makes for your account is Supabase auth — and that only stores which tool you ran and when, never file content.
Why isn't Word/Excel/PowerPoint → PDF included?
Converting Office formats accurately needs a real rendering engine (what Word or LibreOffice use internally) — no browser library does this reliably. Rather than ship a broken version, it's left out.
Does TechDriven Tools have OCR (text recognition)?
Yes — OCR PDF recognizes text in scanned or photographed pages using Tesseract.js, running entirely on your device, and gives you a searchable PDF or a plain text file. Nothing is uploaded for this either.
Can I use this without an internet connection?
Once the page and its libraries have loaded once, yes — the tools themselves need no network access. Signing in and viewing history do require a connection, since those talk to Supabase.
What happens to the "history" if I sign in?
Only a row per tool run — the tool's name and a timestamp. No filename, no file content, ever. You can see the full list any time via the History button.
Are the non-PDF utilities (password generator, JSON formatter, etc.) private too?
Yes — same rule as the PDF tools. Word Counter, Case Converter, Password Generator, UUID Generator, Base64, Hash Generator, JSON Formatter and JWT Decoder all run with plain JavaScript already loaded in this page; nothing you type or paste is sent anywhere.
JSON Formatter, in depth
JSON Formatter pretty-prints or compact-minifies JSON in the browser so API payloads become readable for reviews and diffs.
How JSON Formatter works here
JSON Formatter runs locally in your browser on TechDriven Tools. Inputs stay on your device — nothing is uploaded for this step.
Read every label before running. For JSON Formatter, the controls that change outcomes most are: Beautify vs Minify, paste/load JSON, copy output. Change one control at a time when you are comparing results.
When to use it
Use JSON Formatter when the job matches what the tool is named for — not as a generic substitute for unrelated PDF or data tasks.
Prefer this browser version when the input is sensitive and you want processing to stay on-device with clear option names like: Beautify vs Minify, paste/load JSON, copy output.
If the next step differs (for example you finished and now need a sibling utility), jump to a related tool instead of forcing one screen to do everything.
Teams standardize on JSON Formatter when the alternative is emailing files to a consumer upload site. Document the preferred option defaults (for example the usual quality, corner, or rate) so everyone reproduces the same result.
If JSON Formatter is only one step in a pipeline, write the order down: what happens before, what happens after, and which related tool owns each step. That prevents double-processing and accidental quality loss.
On mobile, prefer moderate file sizes and simpler option combinations. Local processing is powerful, but phones have less memory than desktops for huge scans or megapixel images.
Readable code review. Beautify minified API payloads before commenting.
Compact for transport. Minify pretty JSON before embedding in config.
Spot structural mistakes. Formatting often reveals missing commas before validators run.
Options that change the result
Primary controls
The important controls are: Beautify vs Minify, paste/load JSON, copy output. Change one at a time when comparing outcomes so you know what improved the result.
Run and verify
After you run JSON Formatter, open or inspect the output on the device where you will share it. Keep originals until that check passes.
Boundaries
This page does not replace desktop suites for heavy Office conversion or certified legal e-sign. It covers the focused job described above.
Practical defaults
Start with conservative defaults on JSON Formatter, run once, then adjust. Extreme settings (lowest quality, highest tip, densest QR payload) are for known constraints — not first tries.
Inputs that surprise people
People often misread units or page indexes. Align with the on-screen labels and the total page count or unit selectors before blaming the engine.
Outputs and naming
Rename downloads immediately (date + client + purpose). JSON Formatter may use a generic filename; clear names prevent sending yesterday’s draft.
Accessibility and sharing
After visual tools (watermark/sign/page numbers), skim a page with fresh eyes for contrast and coverage. After data tools, copy results into the system of record your team actually uses.
Privacy
JSON Formatter is designed to run in your browser so your files and text are not uploaded for the core transformation.
Still handle downloads carefully: a private process can still leave sensitive files in your Downloads folder.
Optional accounts on TechDriven Tools, when used, are about lightweight usage metadata — not storing the contents of your JSON Formatter inputs.
If policy requires a vendor DPIA for any online tool, note that local browser processing reduces data transfer risk, but downloaded artifacts still need handling under your retention rules.
JSON Formatter is built to process locally in your browser so sensitive PDFs, images, or text do not need to be uploaded to an unknown server just to finish this job.
Common mistakes
- Beautifying invalid JSON — Fix syntax first with JSON Validator.
- Pasting secrets into random formatters — Prefer local tools for tokens and keys.
- Minifying without a backup — Keep the pretty copy for humans.
Getting reliable results from JSON Formatter
Most failures with JSON Formatter are input/setting issues rather than mysterious bugs: wrong units, wrong page lists, wrong language, or expecting one tool to do a sibling’s job. Re-read the option names, fix the input, and re-run — local tools make iteration cheap.
JSON Formatter accelerates the workflow; it does not replace your judgment or professional advice where required.
Related tools
These related tools commonly sit before or after JSON Formatter in real workflows.
- JSON Validator — Check whether JSON is valid and get a clear error message with location when it is not.
- Base64 Encoder/Decoder — Encode text to Base64, or decode Base64 back to plain text.
- JWT Decoder — Decode a JWT's header and payload to inspect its claims.
Use JSON Formatter when you need this specific job done privately and quickly. Respect what it is not (see mistakes), verify outputs, and chain related tools only when the next step truly differs.
Start from JSON Formatter.
If you arrived from search looking for JSON Formatter, bookmark the tool page itself after this guide — the article exists to teach options and pitfalls, not to replace the working UI.
When something looks wrong in JSON Formatter, reproduce with a tiny sample input first. Smaller fixtures debug faster than a 200-page scan or a 2MB JSON blob.
Share feedback with teammates as option recipes (“Quality 72%, bottom-center numbers, Start at 1”) rather than screenshots alone — recipes transfer cleanly.
From our blog: JSON Formatter vs Validator: What's the Difference (and Why You Need Both)