Field types & inputs

Fourteen field types, every one built in-house. No third-party scripts loading on your visitors’ machines — and nothing that isn’t validated twice

wp-admin · QueryCue — field palette
AaShort text
Long text
@Email
Phone
#Number
Date
Single choice
Multiple choice
Dropdown
Consent
Signature · Pro
File upload · Pro
</>Rich text block
Divider

Everything a real form needs. Nothing it doesn't.

Twelve field types come with the free edition: short and long text, email, phone, number, date, single and multiple choice, dropdown, a GDPR consent box, plus a rich text block and a divider for structure. Two more arrive with Pro — a signature pad and an encrypted file upload.

What’s notable is what isn’t there. No date-picker library, no phone-input library, no signature library. QueryCue’s calendar, its signature canvas and every input are written from scratch, which is why the whole frontend stays small and why nothing your visitors load comes from someone else’s server.

Need several fields on one screen — first name, last name, email? Put them in a group step. Pro adds a two-column layout for pairs that belong side by side.

Validated twice, stored carefully.

Checked as they type

Set a character limit, a minimum and maximum number, a step size, an earliest and latest date. Each is checked in the browser — so a mistake is caught before the visitor moves on.

Checked again on your server

Every rule runs a second time in PHP, including a real calendar check on dates. The browser’s verdict is a courtesy; the server’s is the one that counts.

Order the paths

Each answer is sanitised for its type. Signatures are stripped to a safe allowlist of SVG elements before anything is written to the database.

Let the builder check your work

Uploads are encrypted at rest and stored outside your public uploads folder. Downloads need a signed link, the right capability and a valid nonce — and each access is logged.

The details you only notice when they're missing.

Accessible by default

Errors announce themselves. Choices are grouped for screen readers. Required and invalid states are marked in the markup, not just in colour.

No third-party payload

Every input is self-contained. Nothing phones home, nothing pulls a script from a CDN, nothing to break when someone else’s library changes.

Honest about limits

Uploads reject spoofed file types and refuse executables outright. The rules are enforced where they can’t be edited away — on your server.

Signatures and files get the careful treatment.

A signature is captured on a plain canvas — mouse or finger, no library — and saved as an SVG that the server filters down to a safe allowlist of elements. It renders anywhere, scales to any size, and can’t smuggle anything in.

An uploaded file is encrypted the moment it lands, using libsodium’s authenticated encryption, and written outside your /uploads directory into a folder locked down for Apache, Nginx and IIS alike. The file type is checked against an allowlist and against the file’s actual contents, so a script renamed to .pdf gets nowhere. Downloads are signed, permission-checked and logged; orphaned files are cleaned up daily.

One upload field can take up to ten documents — set the number yourself. A client sending three contracts and a photo of a letter doesn’t need four separate questions. And the limit isn’t a suggestion to the browser: it’s enforced again on your server, along with the file’s identity, when the form is submitted.

Great for

Fields are what the flow carries.

Every field becomes a step, and every answer can steer the path:

Build it with the fields you actually have.

Twelve field types, free. Signature and encrypted uploads with Pro.