How to Design Forms That Work on Small Screens

TL;DR: Use one column, tap targets at least 44 pixels tall, and labels that sit above each field and never disappear. Test on a real cheap Android phone, not your laptop. Plain HTML and CSS will get you most of the way — no paid tools needed.
A checkout form on a 360-pixel-wide phone screen has room for roughly 30 characters per line. That's the whole canvas. Every second column, every 20-pixel button and every placeholder that vanishes mid-typing eats space from the only thing that matters: the customer finishing the form.
Here's how to fix that without hiring an agency or buying a form builder.
Mobile form design starts with one column
Stack your fields in a single column and let each one stretch to full width. Two-column layouts look tidy on a laptop and turn into a cramped mess on a phone. If you have short paired fields (like expiry date and security code on a card), keep them side by side only if each still gets at least 44 pixels of height and a comfortable tap area.
Touch targets are the next big win. Apple's guidelines ask for 44x44 points; Google's Material Design asks for 48x48. In practice: make every button, checkbox and dropdown at least 44 pixels tall, with about 8 pixels of breathing room around it. A pixel, by the way, is just one dot on the screen — 44 of them is roughly the width of a fingertip.
Put your main action button where a thumb reaches easily — the bottom half of the screen. On a 6-inch phone held one-handed, the top corners are a stretch.
Labels beat placeholders every single time
Placeholder text (the grey hint inside an empty box) disappears the moment someone starts typing. Halfway through a 10-field signup, they've forgotten whether that box wanted their name or their company. Put a real label above every field and keep it visible.
Match the keyboard to the job. A phone number field should open the number pad, an email field should show the @ key, and a date field should offer a date picker. In HTML that's usually one attribute, like type="email" or inputmode="tel". It takes seconds and removes hundreds of mis-taps.
Turn on autofill too. Adding autocomplete="email" or autocomplete="cc-number" lets the browser fill fields for the user. Fewer keystrokes on a phone means fewer abandonments.
Then there are error messages. "Invalid input" tells nobody anything. "Enter a phone number with 10 digits, like 98765 43210" tells them exactly what to do — and put it right under the field, not in a popup at the top.
Test it for free before you ship
You don't need a device lab. Open Chrome on your computer, press F12, and click the phone icon in the top-left of the panel. That's DevTools device mode, and it lets you preview your form at 360 pixels wide.
Better still, borrow the cheapest Android phone in your house. Load the form on mobile data, not office Wi-Fi, and fill it in with one thumb while walking. You'll spot the broken layout and fiddly buttons in about two minutes.
Want a score? Run Google Lighthouse (free, built into Chrome DevTools) and check the accessibility report. It flags tap targets that are too small.
What this means for your budget
You don't need a subscription form service. A single-column layout, labels, correctly sized buttons and the right keyboard types are all plain HTML and CSS — maybe 40 lines of code. Paid form builders charge $20–$50 a month (roughly ₹1,700–₹4,200) for features you can add yourself in an afternoon.
What bad forms actually cost you is quieter: abandoned carts, support emails asking "what do I put here?", and phone orders that eat staff time. Fixing the basics is the cheapest conversion work you'll ever do.
One warning: skip heavy JavaScript form libraries for a simple contact or checkout form. Every extra script is another thing that can load slowly on a ₹8,000 phone with patchy 4G.
Key Takeaways
- One column, full width, always — two columns break on narrow screens.
- Make buttons and fields at least 44 pixels tall so thumbs can hit them.
- Labels stay visible above fields; placeholders vanish and confuse people.
- Test on a real cheap phone over mobile data before you launch.
Frequently Asked Questions
How big should buttons be on a mobile form?
At least 44 pixels tall and 44 wide, with around 8 pixels of space between them. Apple and Google both publish this number and it matches a real fingertip.
Should I use placeholders instead of labels?
No. Use both if you like, but the label must stay visible after typing starts. Placeholders alone are one of the most common causes of form confusion on phones.
How do I test a form on a phone without owning one?
Use Chrome's DevTools device mode to preview narrow widths, then ask a friend or colleague to try the form on their phone. One real user finds more problems than an hour of guessing.
Sources
How did this story feel?
Be the first to react
AI assistance. This article was researched and drafted with AI tools and reviewed by our editorial team before publication. We link to sources at the end of every article so you can verify the claims. If you spot an error, please let us know.
Recommended gear
Popular tech picks
Samsung Galaxy S25 Ultra
6.9" AMOLED · 200MP · 5000mAh
Editor's pickView on Amazon →Apple MacBook Air 13-inch (M4)
M4 · 16GB · 13.6" Liquid Retina
Editor's pickView on Amazon →Sony WH-1000XM5
Over-ear ANC · 30h battery
Best headphonesView on Amazon →Affiliate links: we may earn a commission at no extra cost to you.
Weekly tech brief
The tech stories worth your time, every Sunday.
One short email with the most useful guides and gadget picks from the week. No spam, unsubscribe anytime.
Written by
TechPulse TeamThe TechPulse editorial team publishes clear, practical technology guides. Every article is original and written to be understood — not just skimmed. Read our editorial policy.
Comments (0)
No comments yet — start the conversation!
Keep reading

Web Security Headers Every Site Should Set
Five server-side headers block most common web attacks, and four of them are safe to switch on today. Here's what each one does, in plain English.

How to Debug a Slow Page With Browser Performance Tools
A slow page usually has one big culprit, not fifty small ones. Here's how to read the timeline and fix what users actually feel.

CSS Grid vs Flexbox: When to Use Which
A plain-English guide to CSS grid vs flexbox, with shelf and calendar analogies. Learn when each layout tool saves you time and when to mix them.