Browser Kitty
日本語
productivity

Local Form Builder

Build inspection, reception, survey, and checklist forms locally, then export a standalone HTML that can save responses and manage CSV / JSON data on the device.

View on GitHub
Local processing
About your filesFiles and content selected in this tool are processed in your browser and are not uploaded to a Browser Kitty backend.
Operation demo See the basic workflow in a short video.

About this tool

Local Form Builder is a browser-based builder for practical inspection sheets, reception forms, surveys, checklists, and interview sheets. Arrange 14 core field types and edit questions, choices, required state, defaults, and validation in place. You can start blank or from one of six built-in templates such as Event reception, Site inspection, and Survey.

The exported standalone HTML includes validation, local response storage, searchable response history, edit/duplicate/delete actions, CSV export, complete JSON backup/restore, and printing. Form content and responses stay on the device rather than being uploaded to an app server. Each generated form tests persistence before using it and visibly falls back to memory-only storage when durable browser storage is unavailable.

Good for

  • Distribute a site inspection form as one file and keep responses in each device browser
  • Run continuous event reception entries and export the collected responses to CSV later
  • Create a survey or interview sheet that can be used without a network connection
  • Keep form responses on the local device instead of using a cloud form service
  • Copy one standalone form HTML to PCs, phones, or tablets for field use
  • Back up complete response history as JSON and restore it when needed

What it can do

Key capabilities available in this tool.

How to use

  1. Open the tool and start from Blank or one of the six templates such as Event reception, Site inspection, or Survey.
  2. Add text, number, date, choice, heading, and other fields from the field palette or Add field action. On desktop, drag a field directly into the desired position.
  3. Select a field and configure its question, type, choices, required state, helper text, placeholder, default value, and applicable validation.
  4. Switch to Preview, interact with the real controls, and use Check input to run the same validation model used by the exported form.
  5. Choose Normal or Continuous entry mode, set the output filename, and export the standalone form HTML.
  6. Open the generated HTML on the device where it will be used and save responses. Pay attention to any warning when persistent browser storage is unavailable.
  7. Use Response history to search, edit, duplicate, delete, or print entries; export CSV for analysis and JSON for complete backup.
  8. To revise the form later, use Import from HTML in the Builder to read the embedded schema from a previously exported form without executing that document.

Supported

  • Fields: 14 types covering text, textarea, email, phone, number, date, time, radio, select, checkbox, checkbox group, heading, explanatory text, and divider.
  • Templates: Blank, Event reception, Site inspection, Survey, Checklist, and Interview sheet.
  • Validation: required fields, text length, email format, number min/max/step, date range, and checkbox-group min/max selections.
  • Entry modes: Normal shows saved time/count/history actions; Continuous briefly confirms the save, resets the form, and returns to the next entry.
  • Response management: search, edit, duplicate, delete, print blank/completed forms, export CSV, and save/restore JSON backups.
  • CSV: UTF-8 BOM, CRLF, correct escaping, unique headers for duplicate labels, and spreadsheet formula-injection protection.
  • JSON: complete backup containing form metadata, schema, and all responses, with validated Add and Replace restore modes.
  • Storage: generated forms test IndexedDB / localStorage and use only persistence that passes the capability test; otherwise they fall back to memory with a warning.
  • Runtime networking: Builder and generated forms use connect-src 'none' with no runtime third-party library, CDN, remote font, analytics, or telemetry.

Limitations and notes

  • This is not a cloud form service: there are no accounts, server-side response aggregation, shared dashboards, email notifications, webhooks, or automatic cloud synchronization.
  • Conditional logic and calculated fields are not included in v1.0.0.
  • Photo, signature, QR/barcode, GPS, and file-upload fields are not included in v1.0.0.
  • Responses depend on browser-managed storage and may be cleared by browser settings, private-browsing behavior, or device cleanup; save JSON backups for important histories.
  • Storage behavior under file:// can vary by browser, so generated forms rely on a startup capability test rather than assuming persistence.
  • The app is not intended to store passwords, authentication secrets, payment-card data, or similarly high-sensitivity credentials.
  • Large response histories remain subject to browser storage and device-memory limits.

Frequently asked questions

Are forms or responses uploaded to a server?

No. The hosted Builder requires the initial HTML request, but form design, generated forms, responses, and CSV / JSON processing stay in the browser. Both Builder and generated forms use connect-src 'none'.

Can I move the form to another PC or phone?

Yes. Export the form as a standalone HTML file and copy it to a PC, phone, or tablet. Responses are stored in the browser on the device where that form is used.

Can responses be exported to CSV?

Yes. Generated forms can export response history as UTF-8 BOM CSV. Use JSON for complete backup and restoration.

Do responses remain after the browser is closed?

They can when persistent storage is available. Generated forms test IndexedDB / localStorage and fall back to memory with a warning when persistence is unavailable. Save JSON backups for important responses.

Can I edit an exported form again later?

Yes. Import the exported Local Form Builder HTML back into the Builder; it reads only the embedded local-form-schema JSON and does not execute the imported document.

Can respondents attach photos or files?

Not in v1.0.0. Photo, signature, QR/barcode, GPS, and file-upload fields are not included.

Is this a replacement for Google Forms?

It serves a different workflow. Local Form Builder stores responses on each device; it does not provide automatic server-side aggregation, shared dashboards, or notifications like a cloud form service.

Offline version and source code

Both the generated Builder dist/index.html and the form HTML exported by the Builder are standalone HTML files. Form design, validation, response storage, CSV / JSON tools, and printing run in the browser; the hosted Pages version only needs the initial HTML download.

View source on GitHub

Use together

Useful next steps and companion tools, organized around the workflow.

Track roster-based check-in and attendance Check-in Desk Use Check-in Desk when the workflow is specifically roster-based attendance, check-in, or entry/exit tracking rather than a custom form. Run private voting on one phone Pass-the-Phone Vote Use Pass-the-Phone Vote when one shared device needs to collect private votes without showing intermediate results. Inspect CSV or JSON data JSON / YAML / CSV Viewer Use this viewer when you want to inspect, search, or convert CSV or JSON exported from a form.