> For the complete documentation index, see [llms.txt](https://help.imagine.art/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.imagine.art/workflows/app-builder/publish-your-app.md).

# Publish Your App

## Summary

Once your app is built and tested, publishing makes it available to others. Keep it for yourself, share it with your team, or launch it to the Community Marketplace where anyone can use it - and you earn credits every time they do.

***

### How to Publish

#### 1. Confirm your app is ready

Switch to App mode using the toggle at the top of the screen. Walk through the experience as a user would - check that inputs are clearly named, presets work, and the output looks right.

#### 2. Click "Publish App"

Hit the "Publish App" button at the bottom of the left panel. This opens the publishing configuration.

#### 3. "Who should have access?"

Choose where your app should be available:

| Visibility | Who Can See It         | Where It Appears                | Goes Live               |
| ---------- | ---------------------- | ------------------------------- | ----------------------- |
| Private    | Only you               | My Apps                         | Instantly               |
| Team       | All your team members  | Team Apps + My Apps             | Instantly               |
| Community  | Everyone on ImagineArt | Community Marketplace + My Apps | After moderation review |

> Not sure? Start with Private or Team. You can always change visibility later by republishing.

#### 4. Configure your listing

Fill in the details that help others discover, understand, and use your app:

* App Name: A clear, descriptive name. This is the first thing people see in the Marketplace.
* Description: What your app does and what kind of results it produces. Be specific - users search by keywords.
* Cover Image: Your app's thumbnail. Auto-generated from the output, or upload a custom one. A strong thumbnail is the single biggest driver of clicks in the Marketplace.
* Cloning Permission: Choose whether other users can clone (duplicate) your app. Cloning creates an independent copy they can modify without affecting your original. You earn credits from every clone.
* Credit Pricing *(Community only):* Set an additional credit charge on top of the base generation cost. This is your earning per use.

| Earning Tier | Credits You Earn Per Use |
| ------------ | ------------------------ |
| None         | 0                        |
| Low          | 10                       |
| Medium       | 20                       |
| High         | 30                       |

#### 5. Submit

* Private & Team apps go live instantly.
* Community apps are submitted for moderation review. The team reviews for quality and safety, this usually takes a few hours. Once approved, your app appears in the Community Marketplace.

***

### Moderation (Community Only)

Apps published to the Community go through a review before going live. The moderation team checks for quality, safety, and adherence to community guidelines.

Private and Team apps skip moderation entirely and are published instantly.

***

### What's Next

After publishing, head to [Manage Your Apps →](https://claude.ai/chat/manage-your-apps.md) to track metrics, edit workflows, manage versions, and monitor your credit earnings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.imagine.art/workflows/app-builder/publish-your-app.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.