Empty AI login pages are a layering problem: five CSS-only layouts lift coverage from 5.8% to 24.8%
How to make a desktop login page not look empty: 5 layout patterns and a paste-ready AI prompt
Author: ENCI
Core conclusion: A login page looks empty not because it has too few fields, but because the whole screen has only one layer of focus. AI's default is a 340px form floating on a 1440px white background, occupying just 5.8% of the pixels, with zero depth behind it. The fix is not to fill the form, but to add a second layer — a brand zone, ambient light, or a typographic anchor. This article offers 5 layouts you can copy directly, with measured content coverage going from 5.8% to 24.8%, plus a hard-constraint prompt you can paste straight into AI.
📦 Companion resource: 5 login page layouts, runnable comparison page (V0–V5, one-click switching)
Table of contents
- One-sentence conclusion
- Why login pages look empty
- Measure it first: three testable metrics for emptiness
- Five layout patterns (with use cases and trade-offs)
- Measured comparison: six screenshots and a set of numbers
- A paste-ready AI prompt
- Complete runnable code (split column version)
- Comparison table: symptom → cause → fix
- How to choose: a decision table
- Three common pitfalls
1. One-sentence conclusion
Look at this picture first 🛋️: in a 60-square-meter living room, you move out the sofa, the coffee table, and the TV, and leave a single chair in the middle. You're not being "minimal" — you just haven't furnished the place. Anyone walking in would think "this room isn't done yet."
An AI-generated login page is that living room. It treats a 1440px-wide screen as a blank sheet of paper, drops a single 340px form in the center, and leaves the remaining 76% of horizontal space dead. It feels empty not because of the whitespace — whitespace itself is fine — but because there is nothing behind that whitespace.
So the one sentence worth remembering is this:
Empty = one layer of focus + zero background. The right way to fill the page is to add layers, not to add fields.
Section 5 proves this judgment with five sets of measured numbers, and one set is especially counterintuitive: one layout's blank share reaches 91.9% — only 2.3 percentage points lower than the "emptiest" default — yet it does not look empty at all, because there is a layer of light behind it.
2. Why login pages look empty (root cause)
Four causes stack together; remove any one and the problem changes:
① Desktop is treated as a stretched mobile screen. Almost every AI login template comes from a 375px mobile wireframe: one column, centered, stacked vertically. That's correct on a phone, because the screen is narrow and a single column is full width. Moved to 1440px, that single column takes up only 24% of the width; the rest is gap.
② The form itself cannot support the first screen with its information density. A standard login box has 2 fields, 1 button, and 1 "forgot password" line, totaling 286px in height. The first screen is 900px tall — the remaining 614px must be filled by something else, and AI's default answer is "don't fill it."
③ The form is a vertical single-depth structure. Vertical structure works naturally on narrow screens but exposes its weakness on wide ones: the eye travels from top to bottom in one second, then has nowhere to go, and all it can register is "empty."
④ When AI has no brand assets to use, it only knows how to leave whitespace. Ask it to make a login page and it doesn't know what slogan, customer logos, or product screenshots to put there, so it omits everything. It's not lazy — you never gave it second-layer material.
These four causes converge on one conclusion: a login page's size problem is essentially a structure problem.
3. Measure it first: three testable metrics for emptiness
"Empty" sounds subjective, but it can be measured. This article uses three metrics, all computable from a single screenshot:
- Block Count: the number of independently identifiable information blocks on the first screen (title, paragraph, input group, button, logo wall — each counts as one). Fewer than 8 blocks generally reads as thin.
- Coverage: the union area of the bounding boxes of all content blocks ÷ viewport area. Note it's a union — overlapping regions are counted only once.
- Content Box: the smallest enclosing rectangle around all content blocks. It determines where the "visual center of gravity" lands and whether horizontal space is being used.
Stating the measurement method clearly means you can reproduce it: viewport 1440×900, sampled with a 6px grid over the full screen (240×150 = 36,000 sample points total), each point tested for whether it falls inside any content block's bounding box; hits ÷ total gives the coverage. This algorithm lives in the companion demo's measure() function — open the page and run the console to see it for yourself.
4. Five layout patterns
All five layouts below are implemented in pure CSS with no images, so you can swap in your own copy directly. They are judged by the same criterion: what does each one use to supply the second layer?
4.1 Pattern 1: split columns + brand narrative zone (Split Brand)
The left 54% is the brand zone: a deep purple gradient base, grid lines for texture, one 40px proposition, three data-backed value points, and a row of client logos at the bottom. The right 46% is a white form, 380px wide, containing social login and a registration entry.
Why it doesn't look empty: it converts that horizontal 76% of dead space into a narrative zone. With the two columns dark and light, the eye has two clear landing points, and the vertical single-depth problem is completely resolved.
Measured: 16 content blocks, 19.6% coverage, content box 1235×788 — horizontal space is nearly filled.
Use for: B2B products that already have a brand color and a proposition that can stand on its own, with no more than 4 form fields.
Trade-offs: the left column's copy is real brand asset; if it's written vaguely it becomes a marketing poster. On mobile it must collapse to a single column, or the left copy will crush the form.
4.2 Pattern 2: centered card + ambient gradient (Ambient Card)
A full-screen dark base #070a14, two radial lights (purple top-left, cyan bottom-right), a 64px grid with a radial mask overlaid, and in the center a 420px glass card (backdrop-filter: blur(18px) + semi-transparent white border).
Why it doesn't look empty: the background itself is the second layer. The card is the only layer, but it floats in a light field that has direction and brightness variation, so it no longer reads as an unbounded void.
Measured: 8 content blocks, only 8.1% coverage — 2.3 percentage points above the default, with 91.9% blank. The numbers barely change; the perception is completely different.
Use for: tool-type and developer-facing products; when you have no brand visual material at all, this is the cheapest option — pure CSS produces the whole scene.
Trade-offs: contrast on a dark background must be recalculated; using a light theme's #e5e7eb border directly will look muddy. Large-area blur will drop frames on low-end devices.
4.3 Pattern 3: minimal single column + generous whitespace (Typographic Minimal)
A very light warm-white background #fafaf9, left-aligned content, only 420px wide. The main title is enlarged to 46px with tightened letter-spacing; the brand name uses small text with 7px letter-spacing as a top anchor; inputs drop their borders and keep only a bottom line; a vertical SIGN IN — 01 structural line runs along the left side.
Why it doesn't look empty: it doesn't add content — it turns the type itself into graphics. A 46px title block carries the visual weight of an illustration, and the vertical label adds a second axis to the screen.
Measured: 8 content blocks, 11.1% coverage, but the content box stretches to 874×493 with the center of gravity shifted −227px horizontally — visual weight clearly lands on the left half, creating composition.
Use for: consumer tools and design-first products; also suited for scenes about "brand tone" rather than "feature explanation."
Trade-offs: this pattern depends entirely on the copy and font quality; a vaguely written title is genuinely empty. It's also unsuitable for forms with many fields.
4.4 Pattern 4: full-screen product visual + glass card (Product Stage)
The left 60% uses pure CSS to fake a product interface: a sidebar navigation, three KPI cards, and eight gradient bar charts. The right side holds a 440px glass card carrying the login. The background is a dark field built from three stacked gradient layers.
Why it doesn't look empty: it lets users see what the product looks like before they log in. This isn't decoration — it's conversion. The user already knows what they'll see after signing in.
Measured: 10 content blocks, 24.8% coverage — the highest of the five; content box 1249×474, horizontally full, vertically concentrated in the middle band.
Use for: SaaS consoles, data products, monitoring products.
Trade-offs: the fake interface must resemble the real product, or the post-login gap destroys trust. It's also the heaviest of the five visually; push it further and it will steal attention from the form.
4.5 Pattern 5: brand narrative split screen + step-by-step form (Narrative Steps)
The left 44% is a dark narrative zone: a STEP 1 OF 3 label, one proposition, one paragraph of explanation, one customer testimonial (with avatar and identity), and a three-segment progress bar at the bottom. The right 56% holds a three-step progress strip (account → verify → complete) plus the form.
Why it doesn't look empty: the left side answers "why should I register," the right side answers "how to register." It has the highest information density while the division of attention is also the clearest.
Measured: 12 content blocks, 17.5% coverage, content box 1181×796 — vertically nearly full.
Use for: products where registration is the critical conversion step, such as B2B trial applications or products whose value needs explaining.
Trade-offs: every added step adds drop-off; splitting into steps is only worth it when fields exceed 5. Splitting wrongly turns a login into a form-filling exercise.
5. Measured comparison: six screenshots and a set of numbers
The same code, same viewport, same CSS variables — only the layout switches. V0 is AI's default output, used as the control.
Six sets of measured data (1440×900, 6px grid sampling):
| Pattern | Content blocks | Coverage | Blank share | Content box | Horizontal center offset |
|---|---|---|---|---|---|
| V0 AI default | 4 | 5.8% | 94.2% | 340×286 | 0 px |
| V1 Split brand | 16 | 19.6% | 80.4% | 1235×788 | −39 px |
| V2 Ambient card | 8 | 8.1% | 91.9% | 346×433 | 0 px |
| V3 Typographic minimal | 8 | 11.1% | 88.9% | 874×493 | −227 px |
| V4 Product stage | 10 | 24.8% | 75.2% | 1249×474 | −23 px |
| V5 Narrative steps | 12 | 17.5% | 82.5% | 1181×796 | −74 px |
The row worth staring at is V2: a 91.9% blank share, only 2.3 percentage points below the default, with coverage rising from 5.8% to just 8.1% — yet it looks completely not empty. The reason is in the layering, not the pixels — the default's white means "nothing here," V2's dark means "there's light." They are statistically almost equally empty, but perceptually they are two different things.
V3 is equally counterintuitive: 11.1% coverage, 88.9% blank, yet the content box stretches to 874×493 with a −227px center offset. It added no content blocks at all; it just enlarged one title to 46px — font size itself is area.
V1 and V5 (19.6% / 17.5%), by contrast, show something else: the layouts that genuinely use the space have no fewer than 12 content blocks. Block count predicts emptiness better than area does: V0 has 4 blocks, V2 has 8, V1 has 16.
6. A paste-ready AI prompt
Paste the block below verbatim into AGENTS.md, .cursor/rules/ui.mdc, or the start of a conversation. Its difference from a vague "make it look elegant and polished" is one thing: every rule can be counted.
## Login page desktop layout rules (viewport 1440×900)
1. The first screen must have two layers: one form layer, one non-form layer.
Their area ratio must be no lower than 1 : 3 (form ≤ 25%).
2. The form column width is fixed at 360–420px and is forbidden to exceed 420px; the remaining
horizontal space must be occupied by the second layer; leaving large flat white or solid-color
planes is forbidden.
3. The second layer must be "readable information" or "product visual," containing at least 3 information
blocks (proposition / numbered value points / client logo wall / product interface / customer testimonial);
decorative gradients or light spots alone are not allowed.
4. The first screen must have ≥ 8 content blocks. Count them yourself before delivery;
if there aren't enough, add to the second layer — don't fake it with font size.
5. Passing the second-layer check requires satisfying any one of these three:
a. A background visual layer covering ≥ 25% of the viewport (gradient field / illustration / product image);
b. A non-form information area ≥ 30% of the viewport (split brand zone / narrative zone);
c. A main title ≥ 36px and a content bounding box width ≥ 55% of the viewport.
6. Below a 900px viewport, collapse to a single column, shrink the second layer to a 220px
top brand bar, and change the form width to 100% (max 420px).
7. No explanatory text is allowed for these elements: buttons, inputs, checkboxes.
Rules 4 and 5 are the key. Rules that can be counted are what AI actually executes; writing adjectives like "keep it airy" or "mind the whitespace" is the same as writing nothing — a point already verified in the previous 12 advanced UI interactions and their AI prompts: say "add a micro-interaction" and it gives you the plainest scale(0.98); say "spring to 1.05 on release, then settle back to 1.0" and it does exactly that.
7. Complete runnable code
Save the block below as a .html file and double-click to run it. It is the full implementation of Pattern 1: left brand zone + right form, pure CSS with no images, all colors collected in :root variables.
<!DOCTYPE html>
<html lang="zh-CN">
<head>
<meta charset="UTF-8">
<title>Login page · split columns</title>
<style>
/* Design variables: change just this block to reskin */
:root {
--brand: #4f46e5; /* brand primary */
--ink: #0f1115; /* main text */
--sub: #6b7280; /* secondary text */
--line: #e6e7eb; /* borders */
}
* { box-sizing: border-box; margin: 0; padding: 0; } /* width includes padding, columns stay aligned */
body { font-family: -apple-system, "PingFang SC", "Microsoft YaHei", sans-serif; color: var(--ink); }
/* Two-column skeleton: left 54% brand, right 46% form, fills the screen */
.login { display: grid; grid-template-columns: 54% 46%; min-height: 100vh; }
/* Brand zone: gradient + grid + glow, three layers stacked for depth */
.brand {
position: relative; overflow: hidden; padding: 56px 64px;
color: #fff; display: flex; flex-direction: column;
background: radial-gradient(120% 90% at 85% 15%, #4c1d95 0%, #241b5e 45%, #0b1026 100%);
}
.brand::before { /* glow: a light source for the dark background */
content: ""; position: absolute; width: 520px; height: 520px; right: -160px; top: -120px;
border-radius: 50%; background: radial-gradient(circle, rgba(139,92,246,.55), transparent 65%);
}
.brand::after { /* grid + fade mask: creates texture */
content: ""; position: absolute; inset: 0;
background-image: linear-gradient(rgba(255,255,255,.06) 1px, transparent 1px),
linear-gradient(90deg, rgba(255,255,255,.06) 1px, transparent 1px);
background-size: 56px 56px;
mask-image: linear-gradient(160deg, #000 30%, transparent 78%);
}
.brand > * { position: relative; } /* content sits above the decorative layers */
.logo { display: flex; align-items: center; gap: 10px; font-weight: 700; }
.logo i { width: 30px; height: 30px; border-radius: 9px;
background: linear-gradient(135deg, #a78bfa, #6366f1); }
.brand h1 { margin: auto 0; font-size: 40px; line-height: 1.22; letter-spacing: -1px; max-width: 460px; }
.brand p { margin-top: 18px; font-size: 15px; line-height: 1.75; color: rgba(255,255,255,.68); max-width: 440px; }
.points { display: grid; gap: 14px; margin-top: 30px; } /* three value points: support vertical density */
.points span { display: flex; gap: 12px; font-size: 14px; color: rgba(255,255,255,.82); }
.points span::before { content: ""; width: 20px; height: 20px; flex: none; border-radius: 6px;
background: rgba(255,255,255,.14); }
/* Form zone: white background + 380px fixed column width, vertically centered */
.form-wrap { display: flex; align-items: center; justify-content: center; background: #fff; }
form { width: 380px; }
h2 { font-size: 26px; letter-spacing: -.4px; }
.lead { margin-top: 8px; font-size: 14px; color: var(--sub); }
.field { margin-top: 18px; }
label { display: block; font-size: 13px; color: var(--sub); margin-bottom: 7px; }
input { width: 100%; height: 46px; padding: 0 14px; font-size: 14px; border: 1px solid var(--line);
border-radius: 10px; outline: none; }
input:focus { border-color: var(--brand); box-shadow: 0 0 0 3px rgba(79,70,229,.12); }
.row { display: flex; justify-content: space-between; margin-top: 14px; font-size: 13px; color: var(--sub); }
.row a { color: var(--brand); text-decoration: none; }
button { width: 100%; height: 46px; margin-top: 24px; border: 0; border-radius: 10px;
background: var(--brand); color: #fff; font-size: 15px; font-weight: 600; cursor: pointer; }
.foot { margin-top: 26px; text-align: center; font-size: 13px; color: var(--sub); }
.foot a { color: var(--brand); text-decoration: none; }
/* Narrow screens collapse to a single column: the brand zone shrinks to a top brand bar */
@media (max-width: 900px) {
.login { grid-template-columns: 1fr; }
.brand { padding: 28px 24px; min-height: 220px; }
.brand h1 { font-size: 26px; margin: 24px 0 0; }
.brand p, .points { display: none; }
.form-wrap { padding: 36px 24px; }
form { width: 100%; max-width: 420px; }
}
</style>
</head>
<body>
<div class="login">
<!-- First layer: brand narrative zone, responsible for absorbing the horizontal dead space -->
<aside class="brand">
<div class="logo"><i></i> Aurora</div>
<h1>Keep every decision<br>from your team on one page</h1>
<p>Projects, documents, and discussions gathered in a single workspace — a new member sees the full context on day one.</p>
<div class="points">
<span>Tested by a 300-person team; weekly meetings shortened by 40%</span>
<span>Permissions granular down to a single document; external collaboration stays controlled</span>
<span>Every action leaves an audit trail; export for compliance in one click</span>
</div>
</aside>
<!-- Second layer: the form, width locked at 380px -->
<main class="form-wrap">
<form>
<h2>Log in to Aurora</h2>
<p class="lead">Continue with your work email</p>
<div class="field"><label>Work email</label><input placeholder="[email protected]"></div>
<div class="field"><label>Password</label><input type="password" placeholder="••••••••"></div>
<div class="row"><span>Remember me for 7 days</span><a href="#">Forgot password</a></div>
<button>Log in</button>
<p class="foot">No account yet?<a href="#">Request a trial</a></p>
</form>
</main>
</div>
</body>
</html>
After it runs, drag the browser window from 1440px down to 800px: the brand zone first collapses into a 220px brand bar, then the form switches to full width. This step is mandatory for Pattern 1 — skip it and a phone user lands on half a slogan.
8. Comparison table: symptom → cause → fix
| Symptom | Cause | Fix |
|---|---|---|
| The form floats alone in the middle with large white bands on both sides | The whole screen has only one layer of depth; only the middle 340px of 1440px is used | Use Pattern 1; let the brand zone eat that 76% of horizontal dead space |
| Added a gradient background and it still feels empty | The background has color but no information | Add 3 readable information blocks to the background: a proposition, numbered value points, a client logo wall |
| Making the card bigger looks clumsy, smaller looks empty | You're tuning the result instead of the structure | Lock the form column at 360–420px; give every remaining pixel to the second layer |
| A dark background instantly looks cheap | There is base color but no light source | Radial light + grid mask + glass layer; remove one of the three and it becomes a flat color swatch |
| Looks fine on mobile, empty on desktop | A 375px single-column wireframe stretched directly to 1440px | Design the horizontal structure for desktop separately; collapse back to a single column on narrow screens |
| AI generates the same login page every time | The prompt has no verifiable specifications | Use the 7 hard constraints in Section 6; every one can be counted |
9. How to choose: a decision table
| Your situation | Recommendation | Reason |
|---|---|---|
| You have a brand color and a proposition that can stand alone | Pattern 1: split columns | Highest space utilization; the clearest split between narrative and form |
| No visual material at all and it ships today | Pattern 2: ambient card | Pure CSS generates the scene; coverage rises just 2.3 points and it's already not empty |
| Design-led consumer tool | Pattern 3: typographic minimal | Font size and letter-spacing create the anchors; no extra content needed |
| The product itself is the selling point (console, dashboard) | Pattern 4: full-screen visual | Users see the product before logging in; directly serves conversion |
| Registration has more than 5 fields and the value needs explaining | Pattern 5: narrative steps | Left side explains why, right side breaks down the steps, lowering single-page cognitive load |
When choosing, ask exactly one question: do I have second-layer material on hand? With brand copy go Patterns 1 or 5; with a product interface go Pattern 4; with neither, take Patterns 2 or 3. The worst option is to keep adding fields to the form.
10. Three common pitfalls
① Treating "filled" as "not empty." The densest of the five is V4 (24.8%), and it is also the easiest to botch: once the fake interface diverges from the real product, expectations fall flat. "Not empty" means clear layering, not pixel density.
② Left split column with an illustration only and no words. A pure illustration on a 1440px canvas is still a "color block with no information"; a user scanning past it retains nothing. At minimum you need one proposition plus three numbered value points.
③ Forgetting the narrow-screen collapse. If Patterns 1 and 5 don't collapse to a single column on mobile, you get the classic accident: "the left half is all slogans and the form is pushed off the screen." Set the collapse breakpoint at 900px and compress the brand zone to 220px.
If your product doesn't even have copy finalized, the problem isn't at the layout layer — go back and write those three information blocks from Section 6, rule 3 (proposition, value points, testimonial) first, then talk about color.
With brand copy, go split columns; with a product interface, go full-screen visual; with neither, use pure-CSS ambient light to complete the second layer. Don't add fields to the form. What reads as empty is never whitespace — it's nothing behind the whitespace.
This column, Full-Stack Development, covers three threads: frontend engineering, UI design, and AI-assisted development. Every article ships with a runnable demo and a rules file you can paste into your project, updating weekly. To read through in order, subscribe on the column page.