Three problems. Only one is a fault.
“Not working” covers a feature you cannot find, a request that fails, and a picture that came back wrong and the fixes have nothing in common. Two minutes deciding which one you have saves an hour of changing things that were never the cause.
Which of these is actually happening?
Pick the one that matches what you are seeing. Everything after this depends on the answer, and guessing wrong is how people end up reinstalling an app that was fine.
You cannot find it
There is nothing to click, no image option anywhere, and asking for a picture does not produce one.
Looks likeSearching menus, or a chat that answers in words when you asked for an image. Five checks Door BIt fails when you use it
You can reach it, you ask, and something goes wrong an error, a blank, or a wait that never ends.
Looks likeError messages, spinners that do not resolve, images that never arrive. Six checks Door CIt works, and the result is wrong
An image comes back every time. It just is not the one you wanted, or it has something obviously broken in it.
Looks likeGarbled lettering, the wrong number of things, six fingers, a different picture every attempt. Eight symptomsIf the whole app is misbehaving rather than image generation specifically, start with Meta AI not working instead and if you cannot stay signed in, login problems is the page.
Five checks, cheapest first
Four of the five are not faults. Work down the list and stop at the first one that explains what you are seeing.
You are looking for something that does not exist
By far the most common cause. There is no Muse Image app, no menu item and no mode to switch into image generation is a capability inside the Meta AI app, reached by asking for a picture in an ordinary chat. Where it actually lives.
You are not signed in, or signed into the wrong account
Features follow the account, so a second Meta account you forgot about can present a different set of capabilities. Check which one the app is using before anything else. If sign-in will not stick.
Try the same request in the browser
Signed in to the same account. If a picture comes back there, the capability exists on your account and the question is about the app; if it does not, the answer is region or rollout rather than anything on your Mac.
Your country or rollout wave
Which Meta AI features are switched on varies by country, surface and wave, and Meta has not published a feature-by-feature list. An absence of this kind is not a fault and nothing on your machine changes it. Availability.
An old app version
Last on the list because it is the least likely and the most disruptive to act on. Update normally rather than reinstalling, and only if the first four checks came back clean. Updating properly.
Missing is not the same as broken
A feature that has not reached your country, your surface or your rollout wave will look identical to a fault from where you are sitting and no amount of reinstalling, resetting or reconfiguring brings it forward.
If the browser version does not have it either, stop looking for a fix. There isn’t one to find, and the only useful move is checking again in a few weeks.
Six checks, and one that tells you the most
This is the only door with a genuine fault behind it, and the diagnostic that matters is cheap: try the same request in the browser version, signed in to the same account.
Works in the browser, fails in the app → the app. Fails in both → your account, your region, or the service. One test, and half the possibilities disappear.
It is worth doing first because almost everything that goes wrong with image generation is on the far side of the network. The app on your Mac is a 16 MB shell it does not generate anything, so it has very little to break.
That is also why reinstalling is such a poor first move. It is the most disruptive action available and it only addresses the least likely cause.
Try it in the browser first
Same account, same request. This splits every remaining possibility into two groups and costs nothing.
Ask once more, a few minutes later
Transient failures are common with anything server-side. One retry after a pause distinguishes a blip from a pattern, and costs less than any other diagnosis.
Check whether you are rate-limited rather than broken
A limit says so and recovers by itself; a fault errors, blanks or hangs. If you have just generated a great many images in one sitting, suspect the limit first. How metering behaves.
Quit the app properly and reopen it
Not close the window quit. This clears a surprising share of app-side oddities and takes ten seconds.
Sign out and back in
Worth doing when the browser worked and the app did not, since a stale session on one surface explains that pattern neatly. Sign-in trouble.
Update, and only then reinstall
Last, deliberately. Reinstalling is the most disruptive thing here and addresses the least likely cause it is what you do when the browser works, everything else has failed, and you have ruled the rest out. Doing it cleanly.
Eight things that are not faults
This is where most “not working” searches actually belong. Every row below is documented behaviour of how image generation works, which means no amount of troubleshooting will change it but in most cases there is something better to do instead.
| What you are seeing | Fault? | What is actually going on, and what to do |
|---|---|---|
| The words in the image are gibberish | Expected | Rendered text is unreliable across image generators. Generate with a blank area and set the type yourself. |
| I asked for five and got four | Expected | Counts are approximated rather than followed. Generate one and compose the set yourself. |
| It is not my product / my house / that landmark | Expected | You get a convincing relative, never the individual. Use the real photograph why this matters most for products. |
| Hands, fingers or teeth look wrong | Expected | Extremities are a known weak area. Crop tighter, or choose a composition that avoids them. |
| The same prompt gives a different picture | Expected | Generation is not reproducible and there is no seed. The file you saved is the only copy of that version. |
| Regenerating lost the parts I liked | Expected | A new generation is a fresh attempt, not a revision. Edit the image instead. |
| My whole set has drifted out of step | Expected | You chained each image off the last. Anchor to one reference instead. |
| It refused my request | Policy | Content rules are Meta’s to define and enforce. A refusal is a policy outcome, not a malfunction, and rewording to evade one is not troubleshooting. |
| Images arrive corrupted, blank or half-drawn | Fault | This one is genuine. Go to Door B and start with the browser test. |
The pattern across the first eight rows: the tool gives you the neighbourhood, not the address. When a request needs something to be exactly so, that part of the job belongs somewhere else what approximation means in practice.
What not to do while troubleshooting
Do not reinstall first
It is the most disruptive step and addresses the least likely cause, since the app does no generating. It belongs at the end of Door B, not the start.
Do not rewrite the prompt longer
A disappointing result is not a broken one, and a longer prompt rarely fixes it. If your third attempt is a longer second, you need an edit or a reference.
Do not hammer a rate limit
Repeatedly retrying through a limit does not get you through it any faster and burns the allowance you will want when it recovers. Stop, and come back later.
Three things with no fix from where you are
Worth naming so you stop looking. Each is real, none is yours to solve.
The feature has not reached you yet
Rollouts move in waves and sometimes backwards. Nothing you install, reset or configure moves you up the queue, and a VPN misrepresents where you are rather than granting access. Check again later.
It worked yesterday and not today
Usually nothing you did. Limits tighten, waves shift, services have bad afternoons. Run the browser test, then wait rather than dismantling an installation that was fine.
You are on an Intel Mac
The app is Apple silicon only, so the symptom is that it will not install rather than that image generation misbehaves. The browser version is the route on those machines Intel Mac support.
Reporting a genuine fault
If you have worked through Door B and something is truly broken, that goes to Meta’s own support and in-app feedback. We are an independent guide we cannot see your account, cannot fix anything, and cannot escalate on your behalf.
Worth including when you report it: whether it also fails in the browser, what the exact message said, and roughly when it started. Those three facts turn a vague report into an actionable one.
Common questions
I cannot find Muse Image anywhere. Where is it?
There is no separate app or menu item to find. Image generation is a capability inside the Meta AI app, reached by asking for a picture in an ordinary chat, so the most common cause of not finding it is looking for something that was never there where it lives.
Is it missing because it has not rolled out to me?
Possibly. Which Meta AI features are switched on varies by country, surface and rollout wave, and an absence of that kind is not a fault. Nothing you change on your Mac will turn it on early availability.
Generation fails or nothing comes back. What first?
Try the same request in the browser version while signed in to the same account. If it works there the problem is the app; if it fails there too the problem is your account, your region or the service, and reinstalling would have wasted your time the six checks.
How do I tell a rate limit from a fault?
A rate limit tells you it is a rate limit and recovers on its own without you doing anything. A fault gives an error, a blank response, or an endless wait. If you are unsure, stop generating for a while and try once later.
Is a bad result a fault?
Usually not. Garbled text, the wrong number of objects, a product that is not quite yours and a different picture every time are all documented behaviour rather than breakage, and no amount of troubleshooting changes them the eight symptoms.
Why does it refuse some of my requests?
Content rules apply to what can be generated, and they are Meta’s to define and enforce. A refusal is a policy outcome rather than a malfunction, so rewording to get around one is not troubleshooting.
Should I reinstall the app?
Not as a first move, and rarely at all. It is the most disruptive thing on the list and the least likely to help, because almost everything that goes wrong here is account-side, region-side or service-side rather than in the 16 MB app on your Mac.
It worked yesterday and not today. What changed?
Most often nothing you did. Rollouts move in both directions, rate limits tighten, and services have bad afternoons. Check the browser version, then wait rather than dismantling a working installation.
Does an Intel Mac cause this?
An Intel Mac cannot run the Meta AI app at all, so the symptom there is that the app will not install rather than that image generation misbehaves. The browser version is the route on those machines Intel Mac support.
Where do I report a genuine fault?
Through Meta’s own support and in-app feedback, since we are an independent guide and cannot see your account, fix anything or escalate on your behalf.
Most of the time, nothing is broken.
Missing is a rollout, disappointing is by design, and the genuine faults almost all announce themselves in one minute with a browser tab.
Independent guide not affiliated with Meta, and unable to see or fix your account. Report genuine faults through Meta’s own support.