Meta Muse Image: Features, Access & Limits

Muse Image is Meta’s image generation and editing model, announced on July 7, 2026. It accepts text and reference images and can refine an image across turns. Meta describes it as an agentic model that can use search, code, and self-refinement while preparing an output. The official announcement and current image-generation documentation explain those capabilities at different levels of detail.

If you want to use the model, start with a Meta interface or an API provider that explicitly lists it. If you want to prepare a brief first, this site has an original prompt library and a free sample-preview workspace. This website is independent of Meta, and its sample images are not Muse Image outputs.

The most useful first decision is not which adjective to add to your prompt. It is whether you need a new image, an edit that preserves an existing asset, or a repeatable API workflow. That choice determines the references, controls, and review process you need.

First, identify which Muse you found

The name appears in several distinct contexts. Search results can mix official model information, consumer apps, older research, and independent websites with similar branding.

This distinction matters for practical questions. An invite code for an agent is not evidence of access to an image-model API. A benchmark from Google’s research paper does not describe Meta’s model. A third-party site’s free-credit promotion does not establish Meta’s own price or your account’s eligibility.

Check the domain, the exact model ID, and the service that will handle your request before entering a key or paying for generation. A familiar product name in a page title is not enough to identify the underlying provider.

What Meta documents about the model

Generation from a visual brief

A text prompt can describe a subject, setting, composition, and visual treatment. Meta’s documentation shows Muse Image returning an image from that description. For a one-off request, the Images API provides a straightforward generation endpoint. For a continuing creative conversation, the Responses API can carry the process across turns.

That interface choice is more useful than treating every task as a fresh prompt. A standalone background concept can start from text alone. A product campaign where the bottle shape and label must remain unchanged needs a reference and an editing workflow. See the API guide for the endpoint differences.

Editing and multiple references

Meta documents both edits to an existing image and compositions built from several references. The announcement includes examples involving people, objects, clothing, styles, and environments. The API guide describes interleaving text and image inputs so the instruction can identify the role of each reference.

A useful brief tells the model what each image contributes: the product from one photo, the composition from another, and the color treatment from a third. Otherwise, “combine these” leaves important decisions unspecified. Before generation, write down what must be preserved and what may change. After generation, inspect those same details rather than judging only whether the result looks attractive.

These are documented capabilities, not a guarantee that a logo, face, label, or measurement will remain exact in every output. Our review here did not measure edit consistency.

Search, code, and self-refinement

According to Meta’s launch explanation, Muse Image can search for visual or factual references, use code for structured visual tasks, and revise its own drafts. The current API guide also describes automatic grounding and controls for these behaviors.

This changes how a complex request can be approached, but it does not remove your review responsibility. A chart can look well organized while carrying a wrong number. A convincing product image can still alter the package. For a factual graphic, supply the facts you need represented and compare the final image against them. For a real object, compare against your source photograph.

We have not reproduced Meta’s internal evaluations. Historical rankings in a launch post should be read with their original date and conditions, not presented as a current universal ranking.

Where to access Muse Image

Consumer interfaces

The July 7 announcement described availability in the Meta AI app and on meta.ai, in Instagram Stories in the US, and in WhatsApp in limited countries. It also described further rollout plans.

That is a historical launch statement. It is not a complete list of countries, account types, usage limits, or features available on September 25. Open the official interface and check what your account actually offers. A third-party page saying “free worldwide” cannot establish that on Meta’s behalf.

For an occasional personal image, an available consumer interface may be the most convenient starting point. For automated workflows, generated assets inside a product, or repeatable request handling, read the developer documentation instead.

Developer access

Meta Model API lists muse-image-1.0, uses the base URL https://api.meta.ai/v1, and documents generation, editing, and conversational refinement. The developer playground and API use Meta’s own authentication and account conditions.

At the research date, Meta’s pricing documentation lists $0.01 per successfully generated and returned image, with the model’s built-in search included. That is Meta’s API price. It does not describe a consumer subscription or every third-party service using the model. Review the current documentation and your account before relying on a cost estimate.

Our Muse Image API tutorial explains a minimal request, output handling, editing formats, and the distinction between a requested aspect ratio and actual returned dimensions.

Other image-model providers

A third-party provider can offer a different account system, credit scheme, supported model set, or integration experience. Verify the exact listing and request format. Do not assume two services with “Muse” in their name use the same model or preserve the same API parameters.

This site promotes OmniAKey’s image-model catalog for readers exploring image APIs. Use it to inspect the models currently listed and their pricing. This is not a claim that OmniAKey serves Muse Image; check the exact model you intend to call.

Prepare a brief that is easy to evaluate

A useful brief separates the subject, the desired change, and the conditions for success. Consider this original example for a product edit:

Use my product photo as the reference. Preserve the bottle silhouette, cap, label wording, and actual product color. Change the surrounding scene to a pale stone surface with soft side light. Keep the entire bottle visible and leave clear space on the right for a headline. Do not add decorative text or a second product.

This is an example instruction, not a prompt we tested on Muse Image. Its purpose is to make the review criteria explicit. You can inspect the silhouette, label, color, framing, and added objects separately. If the first result changes the cap, the next request can address that one error rather than replacing the whole brief with more style adjectives.

For a new scene, start with the same structure but remove preservation requirements that depend on a reference. State the subject and where it belongs in the frame. Describe one coherent lighting setup. Decide where text will be added later. Then use the provider’s controls for output shape and file format.

Google’s image-prompt guidance likewise discusses subject, context, style, lighting, and composition. Those are useful ways to organize a brief, but model-specific settings remain model-specific. A command suffix copied from another tool is not automatically a supported Muse Image parameter.

Review the image at its intended size

Before publishing an output, evaluate it against the actual task:

1. Subject fidelity: check identity, product shape, proportions, materials, and important accessories against the supplied references.
2. Text and facts: inspect every visible word and number. If exact typesetting matters, consider generating the visual layer and adding final text in a layout tool.
3. Composition: check the final crop, negative space, and whether important edges or faces are cut off.
4. Edit boundaries: compare the areas you wanted changed with the areas you asked to preserve.
5. Usage conditions: check source-image rights, the provider’s output terms, and the requirements of the destination where the image will appear.

This is our recommended review method, not an automated safety or quality test performed by this site. It is intentionally task-specific: a mood-board concept and a customer-facing product listing need different levels of precision.

Meta’s announcement describes Content Seal for images created in its Meta AI app and on meta.ai. Keep that statement within its stated scope. It does not by itself establish the provenance behavior of every API route, export, or independent tool.

What the free workspace here can help with

The Muse Image workspace lets you compose a prompt, append a style direction, plan a square, landscape, or portrait crop, and view curated sample photos. It holds a limited history in the open page so you can reuse the wording.

It does not call muse-image-1.0, evaluate your prompt against that model, or produce newly generated images. A sample photo is a reference for discussion, not evidence that a model followed your instructions. Refreshing the page clears its temporary history.

That makes the workspace useful for planning a brief before choosing a model, but unsuitable for benchmarking image quality. For comparisons between models, run the same permitted inputs through each actual provider, save the settings and outputs, and judge them against a defined task. We have not performed that comparison for this guide.

Next steps

1. Review the free preview and availability page to understand what this site provides.
2. Choose an original prompt example and replace its subject and constraints with your own.
3. Use the API tutorial if you need generation or editing inside an application.
4. Recheck Meta’s official model page for current access and documentation before you generate.