Font Inspector Online
Font Inspector in your browser: free, batch-capable, and limited to 100 MB per server file. The conversion runs on the server in an isolated request. The original source remains available for comparison. Keep the original file while you review the converted copy.
Convert .FONT/* to .JSON
Select a file to begin. Processing details and limits are listed below.
How to use Font Inspector
- 1
Queue the source file
Drop the FONT/* file or files into the uploader. Keep the original until the result has been reviewed.
- 2
Adjust the options
Use the available options for font inspector, or keep the defaults for a standard run.
- 3
Process and download
Run the queue, inspect the JSON result, and download it individually or as a ZIP.
Tool specifications
| Operation | Font Inspector |
|---|---|
| Input | FONT/* |
| Output | JSON |
| Processing | Server-side |
| Maximum size | 100 MB per file on the server. |
| Batch support | Yes, multiple files can be queued; completed results can be downloaded as a ZIP. |
| Quality controls | No quality slider. The output follows the fixed conversion path. |
Why use Font Inspector?
- The tool removes a repetitive manual step while leaving the original available for comparison.
- A separate output file makes review and approval easier before the result is published or sent onward.
- Keeping the source untouched is safer when the result may need to be checked or redone.
- The finished file can be shared or archived without changing the original document.
What changes?
Inspect font metadata. The result is a new file, not an in-place edit, which keeps the original available for comparison.
Processing and limits
- Processing
- Server-side
- Engine
- fontTools
- Maximum size
- 100 MB per file on the server.
- Batch support
- Yes, multiple files can be queued; completed results can be downloaded as a ZIP.
- Quality controls
- No quality slider. The output follows the fixed conversion path.
The file is processed on the server because the conversion requires a server-side engine or a utility operation. The operation is selected by the tool and is not a generic pair conversion.
- Review the output before replacing the original, especially for forms, annotations, or embedded objects.
- The operation depends on the input structure, so a sample is useful before a large run.
- Metadata and interactive elements may need a manual review after processing.
Platform compatibility
The output format is supported by all current major browsers. Desktop and mobile compatibility still depends on the specific application, so test critical files.
When not to convert
- If JSON support is uncertain on the destination device, test a sample before processing a large batch.
- Do not use a converted file as the legal or signed original when signatures or metadata must be preserved.
- Do not overwrite the source; keep both versions until the output has been approved.
Frequently asked questions
- How does Font Inspector work?
- Inspect font metadata. The tool produces a downloadable result and keeps the source file available for comparison.
- Does Font Inspector require an account?
- It is free, requires no account, and adds no watermark. Server uploads are limited to 100 MB per file, and browser-first paths are limited by device memory.
- Will quality change?
- Inspect font metadata. The result is a new file, not an in-place edit, which keeps the original available for comparison.
- Is my FONT/* file uploaded?
- Yes. This conversion uses a server-side engine, so the file is uploaded over HTTPS, processed in an isolated request, and removed after the result is produced.
- How do I process a batch?
- Queue multiple files, run them together, and download the finished results as a ZIP. Each server file is limited to 100 MB, and large batches may take longer.
- What can go wrong?
- Open the downloaded JSON file in the application or database you plan to use, check the structure against the source, and keep the original until the output is approved.