# uip solution bundle

> :::note
**There is no `uip solution bundle` subcommand.** The solution tool does not expose a standalone `bundle` verb. "Bundling" — the step that walks a solution directory, resolves its `.uipx` manifest, collects each project's outputs, and produces an internal `.uis` archive — is an implementation detail of the tool, invoked transparently by other verbs.
:::

:::note
**There is no `uip solution bundle` subcommand.** The solution tool does not expose a standalone `bundle` verb. "Bundling" — the step that walks a solution directory, resolves its `.uipx` manifest, collects each project's outputs, and produces an internal `.uis` archive — is an implementation detail of the tool, invoked transparently by other verbs.
:::

## What you probably want instead

| If you want to… | Use |
|---|---|
| Produce a deployable `.zip` for Orchestrator (`deploy run`) | [`uip solution pack`](./uip-solution-pack.md) |
| Upload the solution to Studio Web for browser-based editing | [`uip solution upload`](./uip-solution-upload.md) |
| Re-scan projects and sync resource declarations in the `.uipx` | [`uip solution resource refresh`](./uip-solution-resource.md) |

Both `pack` and `upload` bundle the solution internally before producing their respective outputs — you do not need to bundle it yourself.

## If you have a .uis file already

Some earlier tooling and external flows produce a `.uis` archive directly. You can hand one to [`uip solution pack`](./uip-solution-pack.md) (as `<solutionPath>`) or to [`uip solution upload`](./uip-solution-upload.md) and the tool will pick it up — the `.uis` path is treated as a pre-bundled solution and skips the directory-walking step.

## See also

- [`uip solution pack`](./uip-solution-pack.md) — produce a deployable `.zip`.
- [`uip solution upload`](./uip-solution-upload.md) — upload to Studio Web.
- [`uip solution` overview](./uip-solution.md).