Write a landing page as one Markdown document, with features, steps and a FAQ as fenced sections, and see it rendered. Free, no account, nothing stored.
Form generator
Build a working form and get its link: pick what you ask, drop what you do not need, choose where answers go. Free, no sign-up, nothing stored.
Say what you are asking people for, untick the questions you do not need, and you get a link. Open it and the form is there, working. There is no account, no dashboard and no database: the form is its address, and nothing about it is stored here.
What it does, and why it is here
Most form builders start you at a blank canvas and end you at an account. You drag fields around, you name them, you argue with a layout, and at the end you are a tenant of a service that holds your form and your answers.
This one starts from the other end: from the errand. You are asking for a message, a booking, an address, a piece of feedback — and each of those has a shape somebody has already worked out. So the tool offers the errand, fills the questions in, and leaves you to remove what you do not want rather than invent what you do. Which is faster, and produces better forms, because the shortest useful version of a form is the one that gets answered.
The second idea is the address. What comes back is not a record in a database but a link that encodes the form. Nothing is written here, so nothing here can go down, be deleted, change its pricing or lose your answers — the form is as durable as the link, and the answers go wherever you tell them, not through us.
What you fill in
- What are you asking for? — pick an errand, and the questions it usually needs arrive already chosen. This is the field that does the work.
- The questions themselves — untick what you do not need, add what you do. Every one you remove is one fewer reason for someone to abandon the form.
- Where do the answers go? — pick the service that will receive them, then paste the address that service gave you. Leave it as it is and nothing is sent at all: the answers stay in the browser, which is a real option for a form you only want people to fill in and read back.
What you get back
- Your form’s address — ready to copy, to open, or to turn into a QR code for a poster or a table.
- A working form at that address, with the questions you kept, laid out and ready to answer.
- How many questions you are asking, and how many of them are required. The number that predicts whether it gets finished.
- An estimate of how long it takes to fill in, in minutes — the figure to look at before deciding a field is “only one more”.
- What the form asks that carries risk — the questions flagged by the field referential: a phone number, a postal address, a date of birth, bank details, anything credential-shaped. When nothing is flagged it says so, in those words. This is the review most form builders leave entirely to you.
What it does not do
It does not receive your answers. That is deliberate and it is the whole design: you name a destination you control, and the answers go straight there. Nothing passes through this page, so there is nothing here to leak, and no account to keep alive.
It cannot build a login form. A password field is refused anywhere it would be sent to a third party, and no form-address should ever be a credential collector.
And a form cannot be edited after it is shared, because there is nothing to edit — the link is the form. Change it and you get a new link; the old one keeps working exactly as it was, which is either the feature or the limit depending on what you are doing.
The tool is in beta. Addresses you have already built will keep rendering the same form; what may still change is what the tool can do.
Writing a form people actually finish
| Do | Why |
|---|---|
| Cut every question you will not act on | Each one costs answers, and a field nobody reads costs them for nothing. |
| Make optional everything that can be | A required field with no good answer ends the form there. |
| Ask for a phone number only if you will ring | It is the field people most often refuse, and it is flagged as risk-carrying for good reason. |
| Say what happens next | “We answer within two days” converts better than any layout change. |
| Keep it under two minutes | The estimate in the answer tells you where you are. |
Questions
Is it really free? Do I need an account?
Free, and there is no account to make — there would be nothing for it to hold.
Where is my form stored?
In its link. The address encodes the form, so nothing is written here and nothing here can lose it.
How do I actually receive the answers?
Choose the service that will receive them and paste the address it gave you. Left empty, nothing is sent and the answers stay in the person’s own browser.
Can I change a form after sharing it?
Not in place. Rebuild it and you get a new link; the old one goes on working unchanged.
Does the person answering need anything?
No — no account, no app, no cookie banner. They open the link and answer.
Can I build a login form?
No. Credential fields are refused where they would be sent on, and a shared address is the wrong place for a password.
Will it stop spam?
There is a decoy field hidden from people and visible to scrapers, which catches the crude bots. A determined one still gets through — nothing short of a real challenge stops those.
Can I put the form on my own site?
Link to it, which is what the address is for. There is no embed script, and that is the point: no third-party code on your pages.
What does the risk line mean?
That one of your questions asks for something the referential singles out — a phone number, an address, a birth date, bank details, a credential. Not a refusal, a prompt: ask whether you need it.
Sources and further reading
- Web form design — Nielsen Norman Group, on what actually costs completions.
- W3C forms tutorial — labels, grouping and error handling that work for everyone.
Explore
More tools like this one
Picked from the catalog by what this page is about — the closest ones first. Each tag opens its whole family.
Record of processing activities template (GDPR Article 30) for controllers and processors, with the Article 35 screening. Free, nothing stored.
Free architecture forms: decision records, quality requirements, constraints, stakeholders, and application, process and flow inventories. Nothing stored.