An interactive form component with clear animated states for labels, validation, errors, submit progress, and success feedback.

Animated Form uses motion to clarify input, validation, submit, error, and success states without slowing the user down.
Use it for lead capture, demo requests, waitlists, onboarding, and contact flows where state clarity matters. The page job is completion: labels, validation, help text, error messages, submit state, and success confirmation should be obvious.
The risk in production is decoration during typing. Animation must never delay input, validation, error discovery, or submission feedback.
You can preview it now. Upgrade to Pro for instant install access.
You can preview it now. Upgrade to Pro for instant install access.
You can preview it now. Upgrade to Pro for instant install access.
A demo-request page can use Animated Form when the team needs clear labels, inline validation, submit progress, error recovery, and a visible success state without adding friction.
Not for flows where animation delays typing, validation, error discovery, payment, or submit feedback.
Keep typing independent from decorative motion, debounce expensive validation, and avoid re-rendering the full form on every keystroke.
Every field needs a label or accessible name, errors need field association, and submit state should be perceivable without relying on colour alone. On mobile, keep inputs large and keyboard-friendly.
| Prop | Type | Default | Description |
|---|---|---|---|
backgroundColor | color | #ffffff | Page background color around the form. |
textColor | color | #111111 | Text color for the form heading and field labels. |
inputBackgroundColor | color | #ffffff | Background color for inputs, textarea, and select controls. |
fieldBorderColor | color | #e5e7eb | Default border color for form controls. |
inputRoundedness | number | 28 | Border radius for inputs and the submit button in pixels. |
duration | number | 0.3 | Transition duration for control focus and button effects in seconds. |
Label, focus, validation, submit/pending, error, and success states. A form page without state rules is not launch-ready.
Inline, tied to the field, written plainly, and not hidden behind animation. Users should know what failed and how to fix it.
Only when motion clarifies state. If it delays typing, hides validation, or makes errors feel playful, it hurts completion.
Yes. A custom version should define content structure, accessibility behavior, motion rules, reduced-motion behavior, source handoff, and implementation notes for the specific page job.
Need a custom effect? Tell us what to create.