Host a JSON file and share it as a link
Put a .json file at a stable URL that any script, app or API client can fetch — and that opens readably in the browser.
Drop your JSON file here
Any other file works too — up to 25.0 MB, or 100.0 MB for a whole site
Free to use. Your JSON file is live at your-name.99helpers.site in about ten seconds.
What is a .json file?
JSON (JavaScript Object Notation) is the standard format for structured data on the web: nested objects and arrays written as readable text. It's what almost every API speaks, and what most configuration and data-interchange now uses in place of XML.
What people use JSON files for
- Static data an application fetches at runtime
- Mock API responses for development and testing
- Configuration files and feature flags
- Datasets published for others to consume
- Exports from tools that speak JSON natively
What opens a JSON file
- Any browser, which displays and often pretty-prints it
- Every programming language, all of which parse JSON
- Postman, curl and API clients
- VS Code and every developer editor
How to host a JSON file
- 1
Drop your JSON file in
Drag it onto the box at the top of this page, or click to choose it. Files up to 25 MB are supported, and nothing is uploaded until you publish.
- 2
Pick an address
Type a name and we'll tell you straight away whether it's free. That becomes the link: config.99helpers.site
- 3
Publish and share
Create a free account — that step exists so the file is yours to update, replace or delete — and the link is live within seconds.
What happens when someone opens the link
The browser displays the JSON as text, and modern browsers format and collapse it so it's actually readable. Because it's served with the proper JSON content type, code can fetch it directly.
Why host a JSON file instead of emailing it?
Sometimes you need data at a URL and nothing more — a config file an app reads, a fixed API response for a demo, a dataset for a colleague's script. Standing up a server for that is absurd; a hosted JSON file is a static endpoint you can publish in seconds and update by republishing.
Worth knowing before you publish
- Validate the JSON before publishing — a single trailing comma will break every consumer.
- Requests from a browser page on another domain are subject to CORS, so a hosted JSON file may not be fetchable from another site's JavaScript; server-side and command-line requests are unaffected.
- Files are cached at the edge, so a republished file can take about a minute to propagate everywhere.
- Never put API keys or secrets in a hosted JSON file; the URL is public.
JSON hosting questions
- Can I use this as a simple API endpoint?
- For read-only data, yes — the URL serves the file with the correct JSON content type, so scripts and applications can fetch it. It's static, so it can't accept POSTs or return different data per request.
- Can JavaScript on my website fetch it?
- That depends on CORS. A hosted file doesn't send permissive cross-origin headers, so browser JavaScript on another domain may be blocked. Server-side code, curl and mobile apps aren't affected.
- Will the browser pretty-print it?
- Modern browsers do, since the file is served as application/json — you get a collapsible, formatted view rather than one long line.
- How do I update the data?
- Republish to the same address. Allow about a minute for edge caches to pick up the change.
Put your JSON file online now
It takes about ten seconds, and you only make an account once the file is ready to go live.