FLUX1.1 [pro] is here
Black Forest Labs continue to push boundaries with their latest release of FLUX.1 image generation model.
Posted October 3, 2024 by
- zeke
If you’re paying attention to text-to-image AI leaderboards, you may recently have noticed a mysterious model named “blueberry” topping the charts.
Well, today the cat’s out of the bag: blueberry is the codename for a new series of Flux models from our friends at Black Forest Labs.
These new models are more powerful than any other open-source image generation models out there, and they are available to run on Replicate today:
🫐 replicate.com/black-forest-labs/flux-1.1-pro
🫐 replicate.com/black-forest-labs/flux-pro
FLUX1.1 [pro] is a new model
FLUX1.1 [pro] is a new, faster, more powerful version of FLUX.1 [pro].
It generates images six times faster than its predecessor FLUX.1 [pro] with higher image quality, better prompt adherence, and more output diversity. Independent benchmarks show it generates the highest quality images compared to other open source models, as of Oct 1, 2024.
Pricing for FLUX1.1 [pro] on Replicate is $0.04 per image.
Here’s an example of how to run FLUX1.1 [pro] using Replicate’s JavaScript client:
Check out the model at replicate.com/black-forest-labs/flux-1.1-pro.
Prompt upsampling
FLUX1.1 [pro] includes a new prompt upsampling feature. It uses a large language model to automatically expand your prompt into a longer, more detailed one. You can use prompt upsampling to get a greater variety of outputs from your prompt.
In the example below, the bottom row is generating images with the prompt “bird”, while the top row is enhancing the prompt using the upsampling feature.
The existing FLUX.1 [pro] model is now twice as fast
The existing FLUX.1 [pro] model is also getting a nice upgrade, with a new version that is twice as fast (at constant quality).
Pricing for FLUX.1 [pro] on Replicate is $0.055 per image.
Here’s an example of how to run FLUX.1 [pro] using Replicate’s JavaScript client:
Check out the model at replicate.com/black-forest-labs/flux-pro.
More Flux stuff
We’ve been big fans of Flux since it was released, and we’re creating a lot of content around it.
To learn more about Flux and get started creating your own fine-tunes, check out these guides:
-
FLUX.1: A new state of the art image generation model from Black Forest Labs (August 2024)
-
Fine-tune FLUX.1 to create images of yourself (August 2024)
-
Fine-tune FLUX.1 with an API (September 2024)
-
Using synthetic training data to improve Flux finetunes (September 2024)
Sign in to highlight and annotate this article

Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
modelrelease
5 Patterns for Building Resilient Event-Driven Integrations
Point-to-point integrations are easy to build and easy to break. You wire up an API call from one system to another, it works in testing, and then a 30-second downstream outage in production causes a cascade of failures, lost state, and a manual cleanup effort that takes longer than the outage itself. Event-driven integration patterns address this directly. They decouple the systems involved so that no single failure propagates through the entire integration chain. The tradeoff is upfront design work, but the operational stability that results is not comparable to the alternative. Here are five patterns that appear in most well-built event-driven integrations, with examples of when and why each one matters. 1. Queue-Based Event Processing What it is: Instead of processing webhook events or

Choosing an AI Agent Orchestrator in 2026: A Practical Comparison
Running one AI coding agent is easy. Running three in parallel on the same codebase is where things get interesting — and where you need to make a tooling choice. There's no "best" orchestrator. There's the right one for your workflow. Here's an honest comparison of five approaches, with the tradeoffs I've seen after months of running multi-agent setups. The Options 1. Raw tmux Scripts What it is: Shell scripts that launch agents in tmux panes. DIY orchestration. Pros: Zero dependencies beyond tmux Full control over every detail No abstractions to fight You already know how it works Cons: No state management — you track everything manually No message routing between agents No test gating — agents declare "done" without verification Breaks when agents crash or hit context limits You become

How AI Is Changing the Way We Build Online Businesses
Not long ago, building an online business meant: months of development hiring developers large upfront costs Today? AI has completely changed the game. Now, one person can go from idea → to revenue faster than ever before. And this shift is just getting started. ⚠️ The Old Way vs The New Way Before AI: Build everything from scratch Spend weeks on infrastructure Launch slowly Iterate even slower With AI: Build faster Automate key tasks Launch quickly Iterate in real time The difference is massive. 🧠 AI Is Reducing the Cost of Building One of the biggest changes: 👉 Building is no longer the bottleneck AI helps with: generating content writing code automating workflows handling repetitive tasks What used to take weeks… 👉 now takes days ⚙️ Infrastructure Is No Longer the Hard Part Another s
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.

![FLUX1.1 [pro] is here](https://replicate.com/_content/assets/cover.KlUZSq-3.webp)



Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!