GPT Image 2.5 Sunburst credit costs increased significantly overnight without notice
I'm reporting a sudden and significant increase in generative credit costs affecting the entire GPT Image 2.5 model family in Adobe Firefly, including both Sunburst and Flare.
1. What happened?
On November 5, 2026, generating a 2K image using GPT Image 2.5 Sunburst at High quality cost 15 generative credits.
Today, November 6, the exact same configuration suddenly costs 40 credits — an increase of approximately 167% overnight.
After investigating further, I discovered that this issue is not limited to Sunburst. GPT Image 2.5 Flare is showing the same unusually high credit costs. The issue affects all available resolutions (1K, 2K, and 4K) and quality settings.
2. Current credit costs
The following prices (in generative credits per image) are displayed for BOTH GPT Image 2.5 Sunburst and GPT Image 2.5 Flare:
| Quality | 1K | 2K | 4K |
| Low | 5 | 5 | 10 |
| Medium | 15 | 20 | 30 |
| High | 30 | 40 | 60 |
| Extra High | 40 | 70 | 100 |
| Max | 70 | 100 | 130 |
For example:
-
2K High increased from 15 to 40 credits overnight (+167%).
-
2K Max now costs 100 credits, and 4K Max costs 130 credits per image.
3. Why this is concerning
Image generation for professional creative work requires multiple iterations and prompt adjustments. With the current pricing, even a small number of generations quickly depletes a monthly credit allowance. This pricing jumped overnight across all resolutions and quality levels for both models without any official announcement, release notes, or advance notice.
4. Steps to reproduce
-
Open Adobe Firefly's image generation interface.
-
Select GPT Image 2.5 Sunburst or GPT Image 2.5 Flare.
-
Switch between 1K, 2K, and 4K resolutions and check the displayed credit costs across Low, Medium, High, Extra High, and Max quality before generating.
5. Questions & expected resolution
-
Is this an intentional pricing increase or a credit calculation bug affecting the GPT Image 2.5 model family?
-
If this is a bug, when will the previous credit pricing be restored, and will users who were overcharged be refunded the credit difference?
-
If intentional, why was a 167% increase implemented overnight without advance notice or an update to the official documentation?
