Replicate — FLUX model playground

Dev ToolsSee it livereplicate.com

A public model page shows an input form beside a built-in output example and a sign-in notice.

Replicate — FLUX model playground — captured interface — Viewport capture · opening screen

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

AI interfaces

Why this pattern works

Keep model parameters alongside an example output and make access requirements explicit.

Design notes

Surface: A public model page shows an input form beside a built-in output example and a sign-in notice.
Navigation: Platform header, model identity and playground/API tabs.
Layout: Two-column input/output workspace.
Density: Medium-high
Color: White, black and pale yellow access notice
Type: Compact developer labels with a clear model title.
Pattern: Keep model parameters alongside an example output and make access requirements explicit.
States: Built-in example visible; running this model requires sign-in. No generation performed.
Don't: Adapt the layout to your own product and supported capabilities; write your own examples and keep important actions clearly labeled.

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: Replicate — FLUX model playground
Source: https://replicate.com/black-forest-labs/flux-schnell
Swipefile reference: https://swipefile.design/ref/ai-next-replicate-flux/
Captured: 2026-09-06. 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: A public model page shows an input form beside a built-in output example and a sign-in notice.
- nav: Platform header, model identity and playground/API tabs.
- layout: Two-column input/output workspace.
- density: Medium-high
- color: White, black and pale yellow access notice
- typography: Compact developer labels with a clear model title.
- pattern: Keep model parameters alongside an example output and make access requirements explicit.
- states: Built-in example visible; running this model requires sign-in. No generation performed.
- dont: Adapt the layout to your own product and supported capabilities; write your own examples and keep important actions clearly labeled.

Useful for: Keep model parameters alongside an example output and make access requirements explicit.

## 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: Keep model parameters alongside an example output and make access requirements explicit.

Replicate — FLUX model playground

Make it your own

Keep exploring