What started as a curiosity on March 30th has quietly grown into something more ambiguous. The first thread asked a pointed question: when a user describes themselves in text and asks ChatGPT to generate an image featuring them, why does the system redirect and ask for a photograph instead? It reads as a friction complaint — the kind of thing that surfaces when a product's behaviour doesn't match user expectations. That alone might have stayed buried. But then, nearly a month later on April 22nd, a second thread appeared asking almost the opposite question: how do you stop ChatGPT from generating images at all? Two users, two opposing frustrations, both pointing at the same system behaving in ways they didn't want. One can't get it to work the way they intend. The other wants it to stop working entirely. Between those two poles sits the actual story — ChatGPT's image generation logic is not behaving consistently or predictably enough for a meaningful slice of users to feel in control of it.
If confirmed, here is what this means. OpenAI has invested heavily in positioning image generation as a native, seamless capability within ChatGPT — not a bolt-on, not a separate tool, but something that understands context and responds to natural language the way the rest of the model does. If users are routinely hitting walls when requesting personalised images, or finding themselves unable to suppress image generation when they don't want it, that friction cuts against the core promise. The implications ripple outward: trust in the interface erodes, power users develop workarounds that become load-bearing habits, and the perception of ChatGPT as a coherent product takes a quiet but real hit. Neither complaint on its own would matter much. Together, they suggest the controls around image generation — when to trigger it, when to ask for more input, when to hold back — are not yet calibrated to the range of people using them.
Watch for any official documentation changes from OpenAI around image generation permissions or prompting guidelines, and pay attention to whether these complaints begin appearing in tech press or accumulate further in the community forums — that would shift this from pattern to confirmed friction.
<!-- SC_OFF --><div class="md"><p>Any else getting this? It won’t stop going into image generation! I keep saying we’re discussing a story only. But it often replies by creating
<table> <tr><td> <a href="https://www.reddit.com/r/ChatGPT/comments/1tf9l3h/watermarks_have_now_been_added_to_images/"> <img alt="Watermarks have now been added to images."
<table> <tr><td> <a href="https://www.reddit.com/r/ChatGPT/comments/1x60aeu/is_it_just_me_or_are_the_image_censorship_rules/"> <img alt="Is it just me or are the image censorship
<!-- SC_OFF --><div class="md"><p>It seems image generation in general has gotten so bad. I spent all morning trying to promt a simple app icon. To the point I was trying to get
<!-- SC_OFF --><div class="md"><p>I use ChatGPT only to create images of my DnD characters. The past day it keeps having problems. I will give it some images to referance, ask it
<!-- SC_OFF --><div class="md"><p>So I just noticed that the web interface got a silent update, now when you paste very long text, instead of pasting it inline it becomes a
<table> <tr><td> <a href="https://www.reddit.com/r/ChatGPT/comments/1t6pfv6/gptimage2_is_not_a_better_midjourney_its_the/"> <img alt="GPT-image-2 is not a “better Midjourney.”
<table> <tr><td> <a href="https://www.reddit.com/r/ChatGPT/comments/1shh5aj/anyone_else_get_this_issue_with_image_generation/"> <img alt="Anyone else get this issue with image
NewsHive monitors these sources continuously. All signal titles above link to the original reporting.
Intelligence by NewsHive. Need help navigating what this means for your business? Contact GeekyBee →