Updated October 24, 2026
Form.io is named for the form because the form’s JSON sits at the center of everything the platform does. One JSON schema defines what the user sees, the shape of the data that gets submitted, and how the REST API handles that data, so building the form gives you all three at once.
You would think we’re named Form.io because we help you make forms.
We do help you make forms, fast, but that’s not the reason for our name.
Our name has to do with the sauce—the secret elixir that’s at the very core, the very center of everything we do.
We’ve said in the past that we deliver JSON-powered forms, JSON-powered APIs, and JSON-powered databases.
But what does that actually mean?
What JSON Is, in Plain Terms
First, let me just briefly explain JSON. Bear with me here—trust me and keep reading.
JSON is data. It’s written as name/value pairs. Don’t worry about that.
Know this: It’s easy to read and it is largely a language-independent data format. That means it doesn’t matter a whole lot what programming language you’re using. The top languages can all handle it.
Because of these things, it’s become the standard format for data exchange. Google, X/Twitter, and a whole bunch of companies use it and rely on it.
JSON is powerful. It’s good.
Where MongoDB and NoSQL Databases Fit In
Then there’s MongoDB, which is a NoSQL database. Without going into the nitty gritty, these types of databases are generally cheaper and easier to maintain. You can distribute data easier, their data models are simple, it’s fast, it scales well, it’s flexible, and a bunch of other stuff.
There are also drawbacks with NoSQL databases, one of them being that all the data is unstructured. In other words, you need to have well-defined indexing, otherwise things can get out of hand.
Still with me?
In general, a lot of people think the pros outweigh the cons.
So where am I going with this?
Why a Form.io Form Is Defined in JSON Instead of HTML
The Form.
You know them as boxes on a web page that you fill in to submit. You might even know they’re made of HTML.
Yes, but, our forms aren’t defined as HTML. They are defined by JSON (then rendered as HTML) when you need them.
“Okay, what’s the big deal?” you might ask.
Here’s the sauce, the secret elixir:
- The JSON of the form represents the model of the UI elements.
- The same exact JSON (aka a “schema”) ALSO defines the contract between the client and the server of the data submission. This means you can achieve structured, deterministic databases in MongoDB.
- The same exact JSON ALSO governs the behavior of the server when it receives a request, the CRUD (Create, Read, Update, Delete) interface for the REST API.
That’s killing 3 birds with one JSTONE.
All 3 of these things have been done before us. But we built Form.io to put them all together.
And when you put them altogether, know this:
The FORM rules.
And I mean that in a literal sense.
When you drag and drop to create a form in Form.io, you are accomplishing 3 things at once for a developer. That’s power. That’s speed. That’s efficiency.
All so you can put your data in, and get your data out.
One more thing from the Wizard of wizards:
Form.io can represent more than just what you think of as “forms”. Form.io is more about “FORM-ing something” as it is the “FORM-of something”. With Form.io, you are the creator. You create. You “FORM” new components. It IS the very definition of composable architecture! And there are so many great things to come!
What the JSON Form Gives Developers Today
Here is what that one JSON schema does for you in Form.io now.
- One schema, validated twice: Validation rules live in the form JSON and run in the browser and again on the server when the submission arrives, so both layers behave the same way.
- Logic that travels with the form: Conditional logic, including JSON Logic for more complex conditions, is stored in the schema, so it moves with the form when you export it or migrate it between environments.
- An API with every form: The drag and drop builder outputs the JSON schema and the REST API for each form at the same time, and if you already have a schema written, you can import it.
- Render it in your own app: The open source renderers for React, Angular, Vue, and plain JavaScript turn the schema into a working form inside your application, styled with your own CSS and without iframes.
- Change it once: When someone edits a form in the builder, the change shows up everywhere that form is deployed.
Sources: Forms From JSON: How Schema-Driven Architecture Powers Dynamic Forms, JSON Forms, and How Form.io Works. To see how Form.io compares with other schema-driven form libraries, read JSON Schema Forms Compared: RJSF vs JSON Forms vs SurveyJS vs Form.io. For the bigger picture behind Travis’s point about composable architecture, see The Long-Term Strategy of Composable Software, or tell us what you are building.
