
SDXL sits in an awkward and useful place: it is old enough to be completely settled, and good enough that a great deal of production work still gets done with it. Newer models get the headlines, but "newer" and "better for your job" are different claims.
This guide covers the case for SDXL specifically, what the open image tools actually give you, how local generation works in practice. And — the part that decides commercial questions — where the licensing line sits.
What open image quality actually means
Open image generation gives you three things a hosted service cannot: unlimited runs with no credit counter, no queue behind anyone else, and images that never leave your machine. For iteration-heavy work — finding a look, testing a composition, generating a hundred variations of one idea — that is worth more than any single quality difference.
Production visuals is where SDXL is a genuine answer rather than a compromise. Flexible generation, strong editing capabilities, and the maturity that comes from being widely deployed, all count for something when a pipeline has to be predictable.
| Open/local (SDXL) | Hosted service | |
|---|---|---|
| Runs | Unlimited, on your own machine | Credit-limited |
| Queue | None — it is your own | Shared, and you may have to wait |
| Data | Never leaves your machine | Goes to the provider |
| Setup cost | Time + hardware | Zero |
| Batch work | Free after the machine exists | Paid per image |
How local generation is set up
The pattern is always the same, whichever tool you pick: you obtain model weights, install a runtime, load the model, then run it against prompts and settings until the output matches what you want.
Two practical points that save real time. First, a seed lets you reproduce an image exactly. Change the prompt without noting the seed and you cannot get back to the version you liked. Record it every time.
Second, layer the iteration. Establish composition and subject at a cheap resolution, then move to full resolution only once the framing is right. Re-rolling at full quality while you are still deciding the composition is the most common waste of local compute.
Our Ollama guide covers the runtime and hardware side for text models; the principles carry over, and the memory requirement is higher.
But is SDXL still the right pick?
Honestly: often yes, and the test is specific. Choose it when:
- You need unlimited runs and are worried about the credit meter
- You need predictable, settled behaviour — a new model changes every month, SDXL does not
- Your pipeline needs one repeatable step that has to run again and again
- Data must not leave your machine
Choose something else when you need the highest possible quality on a hero image and can afford a hosted run, or when the tool needs a level of prompt adherence you would rather not fight.
The "which is newest" framing is the wrong question for image work. What matters is which one you can run a hundred times and get the same kind of result.
Licensing: read this before commercial work
This is the section that decides real projects, and it is the one most often skipped. Open weights and a commercial licence are different things. Running a model locally is free; using its output commercially is governed by the licence that ships with it.
Before any client or brand work, check two things: what the model licence permits for commercial output, and whether it requires attribution or restricts certain uses. Where you are unsure, the model card is the authoritative source — not a forum answer, and not a tool page including this one.
Our general position is on the editorial policy page: the licence answers the licence question, and we will not guess at it on a tool page.
Common mistakes
- Not recording the seed. A favourite result you cannot reproduce.
- Iterating at full resolution. Decide the composition first; the cost comes second.
- Equating a free licence with free output. Running it is free; commercial use is a separate question.
- Underestimating setup. Weights, runtime, memory, settings — four separate steps, and the first takes the longest.
Verdict
Who it suits: anyone with volume, a repeat pipeline, or a data-handling requirement that rules out a hosted service — and anyone who wants predictable settled behaviour.
Who it does not suit: a single hero image where maximum quality matters more than cost, or anyone unwilling to do the one-time setup.
Frequently Asked Questions
Is SDXL still as good as newer models?
Do not judge it by model identity at the start. Run one test on your own work — composition, style, output — and the model that gives you predictable results is the right pick. SDXL's advantage is still settled behaviour, not being the newest.
How much hardware do I need to generate locally?
It depends on model size, and the exact minimum is written on the model card — that is the authoritative source. Larger versions need more memory; smaller versions were built to run on an ordinary laptop.
Can I use SDXL output commercially?
That is a licence question, and the answer is on the model card. Open weights do not mean a commercial licence. Read the licence before doing client or brand work — a tool page or a forum answer is not enough.
Why does every image look different when the prompt is the same?
Fix the seed. Note the seed on every generation, and only then can you rebuild the same image. Without the seed you cannot reproduce your favourite result.