Learn how to replicate Hires.fix in Fooocus using the built-in Upscale workflow, with step-by-step guidance, FAQs, and pro tips for all users.
Step 1 — Generate an Image
- Open Fooocus
- Generate your image normally
- Let Fooocus choose its recommended resolution
- Do not force ultra-high resolutions (this causes blur & instability)
- Pick the best image from the batch
Why this matters:
Hires.fix (and its Fooocus equivalent) works best when the composition is already correct. Upscaling does not fix bad anatomy or framing — it refines detail.
Step 2 — Send Image to Upscale
- Click Input Image
- Drag your chosen image into:
“Upscale or Variation”
- Make sure you are not in prompt-generation mode anymore
You are now refining an existing image)
Step 3 — LOCK the Image
This is where most people mess up.
- Open Advanced
- Disable randomness
- Set Seed = 0
- Turn Random OFF (if visible)
✅ This ensures:
- The image structure stays the same
- Fooocus refines instead of re-imagining
This directly matches Reddit + YouTube advice and explains why people saw unwanted changes before fixing the seed.
Step 4 — Choose the Correct Upscale Mode
✅ Recommended (Closest to Hires.fix)
⚠️ Avoid for Hires.fix-style refinement
- Fast 2× → acts more like a traditional upscaler
Why non-fast matters:
It performs diffusion-based refinement, closer to img2img / hires.fix behavior.
Step 5 — Generate
Use 1 Image Only
- Set Images = 1
- Click Generate
You now get:
- Higher resolution
- Sharper textures
- Cleaner edges
- Better micro-details
🎉 This is the Fooocus equivalent of Hires.fix
🧠 Pro Tips (Power Users)
🔹 Pro Tip 1 — 1.5× vs 2×
- 1.5× → subtle refinement, safer for faces
- 2× → maximum detail, riskier for artifacts
🔹 Pro Tip 2 — Faces Changing?
- Disable Enhance temporarily
- Use non-fast upscale
- Avoid prompt edits during upscale
🔹 Pro Tip 3 — Best Hires.fix Quality
- Generate base image
- Upscale 1.5× (non-fast)
- Upscale again 2× (optional)
- Stop before artifacts appear
(This mirrors multi-pass hires.fix workflows in A1111)
🔹 Pro Tip 4 — When NOT to Upscale
- Bad anatomy
- Crooked faces
- Broken hands
- Wrong composition
Fix those before upscaling.
Fooocus Upscale (“Hires.fix”) FAQs
Quick answers for beginners, intermediate users, and power users.
Beginner
Intermediate
Advanced
Upscale • Seed • Fast vs Non-Fast
Beginner
Best practice
Why not just generate at high resolution first?
+
Because direct high-res generations often trade stability for pixels:
- More blur or “mushy” texture
- Less stable composition (poses/structure drift)
- More artifacts (weird edges, noise, odd micro-details)
Pro tip
Think “hires.fix philosophy”: stability first, detail second. Generate a clean base, then upscale/refine.
Intermediate
Troubleshooting
Why did my image change instead of upscale?
+
Most commonly, Fooocus is producing a variation because something is still allowing randomness or prompt drift:
- You left Random Seed on
- You used Variation instead of Upscale
- You changed the prompt during upscale (can re-interpret content)
Fix checklist
Set Seed = 0, turn Random off (if shown), remove prompt edits, then use Upscale only.
Intermediate
Choosing settings
What’s the difference between Fast and Non-Fast (2×)?
+
Fast vs Non-Fast changes how much “refinement” happens during upscale:
- Fast 2×: quicker, more like a traditional upscaler (less re-detail)
- Non-Fast 2×: stronger refinement, closer to a hires.fix/img2img feel
Rule of thumb
Use Non-Fast when you want a hires.fix-like result. Use Fast for quick enlargements when you don’t want extra changes.
Advanced
Automation
Does Fooocus have an automatic “Hires.fix” mode?
+
Not officially as a single always-on toggle like A1111.
However, the community references automation approaches such as:
- GitHub feature requests for auto-upscale behavior
- Debug / Advanced experimental toggles (varies by build)
- Enhance-based workflows that refine outputs
Pro tip
If your build includes it, look under Advanced/Debug for automation-style options. Otherwise, the reliable path is: generate → Upscale (2× non-fast).