Skip to main content
Participating Frequently
July 22, 2026
Answered

Firefly Boards “Vary” is suddenly using Google Gemini instead of Firefly and I can’t change the model

  • July 22, 2026
  • 8 replies
  • 99 views

I’m having an issue with Firefly Boards that just started today.

 

When I click Vary on an image, it automatically defaults to the Flux model, which costs 45 credits per variation. Yesterday, the same workflow was using the Firefly model as expected.

 

The problem is that I can’t find any way to switch the model back to Firefly. There doesn’t seem to be a model selector, so I’m stuck with Gemini.

 

I’ve tried refreshing the page, clearing cookies/cache, and starting a new board, but the behavior is the same.

 

Is anyone else seeing this? Is this a bug, a recent change, or is there a way to change the model back to Firefly for image variations?

 

 

    Correct answer caroline_edits

    Hey JCTremblay! Currently, there is no manual way to change the model when using the Vary feature. Sorry about that! We know it's a feature request for the future.


    Caroline

    8 replies

    jctremblay
    Community Expert
    Community Expert
    August 23, 2026

    @Hajar Toutsi My FF Board Vary functions is using Flux2[Pro]. How to change it?

    caroline_edits
    Community Manager
    caroline_editsCommunity ManagerCorrect answer
    Community Manager
    September 1, 2026

    Hey JCTremblay! Currently, there is no manual way to change the model when using the Vary feature. Sorry about that! We know it's a feature request for the future.


    Caroline

    jctremblay
    Community Expert
    Community Expert
    September 1, 2026

    I know but Flux2[Pro] is producing really bad/ugly results.

    Hajar Toutsi
    Community Manager
    Community Manager
    July 23, 2026

    Hi bcoller,

    Thank you for providing the screenshot, that gives us everything we need! You don't need to worry about recording a video, as the screenshot is completely sufficient and we were able to reproduce and observe the exact same behavior on our end.

    I am escalating this internally with the product team right now to confirm whether this default model routing for image variations is a temporary issue or the new approach moving forward.
    I will follow up and share an update here as soon as I get confirmation from them.

    Hajar

    bcollerAuthor
    Participating Frequently
    July 23, 2026

    Great. Thank you for the help, Hajar!

    N8.
    Community Expert
    July 23, 2026

    Hey ​@bcoller 
    Could you make a short video of the issue?  This will help a lot.

    cheers

    Nate