Facebook — Sign in

Forms & OnboardingSee it livefacebook.com

A visual introduction occupies the left side while a compact sign-in form and account-creation route sit on the right.

Facebook — Sign in — captured interface — Viewport capture · opening screen

Source capture · 2026-09-05Open full image ↗

Forms & onboarding

Why this pattern works

Consumer account entry that needs to explain the product alongside authentication.

Design notes

Surface: Facebook public sign-in page.
Navigation: Minimal product navigation; recovery and account creation stay near the form.
Layout: Wide split screen with imagery and a headline on the left and stacked fields on the right.
Density: Low, with clear spacing between authentication choices.
Color: White, dark text, blue primary action, colorful content imagery.
Type: Large sans introductory message with compact form labels.
Pattern: Separate the product promise from the task-focused form while keeping both visible.
States: Signed-out state with recovery and new-account links; no login was attempted.
Don't: Keep recovery and alternative account paths visible rather than burying them in a footer.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Facebook — Sign in
Source: https://www.facebook.com/
Swipefile reference: https://swipefile.design/ref/popular-facebook-sign-in/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Facebook public sign-in page.
- nav: Minimal product navigation; recovery and account creation stay near the form.
- layout: Wide split screen with imagery and a headline on the left and stacked fields on the right.
- density: Low, with clear spacing between authentication choices.
- color: White, dark text, blue primary action, colorful content imagery.
- typography: Large sans introductory message with compact form labels.
- pattern: Separate the product promise from the task-focused form while keeping both visible.
- states: Signed-out state with recovery and new-account links; no login was attempted.
- dont: Keep recovery and alternative account paths visible rather than burying them in a footer.

Useful for: Consumer account entry that needs to explain the product alongside authentication.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Consumer account entry that needs to explain the product alongside authentication.

Facebook — Sign in

Make it your own

Keep exploring