> ## Documentation Index
> Fetch the complete documentation index at: https://e2b.manicule.dev/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://e2b.manicule.dev/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://e2b.manicule.dev/api/mcp.
> Every agent surface: https://e2b.manicule.dev/.well-known/llms-manifest.json

# Can I make a template public so other projects can use it? (/docs/faq/public-templates)

<!-- agent-signals: reading_time_min: 1 · est_tokens: 324 · updated: 2026-07-30 -->
Related: [How do I increase my concurrency limit?](/docs/faq/increase-concurrency.md), [Do paused sandboxes count toward the concurrency limit?](/docs/faq/paused-sandboxes-concurrency.md), [Is there a limit on how many templates I can create?](/docs/faq/template-limit.md), [Can I run sandboxes in the EU?](/docs/faq/eu-region.md), [Why does iptables fail with 'xt_owner module missing' in a sandbox?](/docs/faq/iptables-xt-owner.md), [Why does pip install fail when building a template?](/docs/faq/pip-install-error.md)

Yes. By default, templates are scoped to the project that built them, but you can publish a template to make it usable by any other E2B project.

## Publishing a template

You can publish a template in two ways:

### From the dashboard

Open the [Templates tab](https://e2b.dev/dashboard?tab=templates), find the template, and toggle it to public.

### From the CLI

Use the [E2B CLI](/docs/cli) to publish a template you've already built:

```bash
e2b template publish <template-name>
```

## Using a public template

Once published, other projects can create a sandbox from your template by referencing it with the full namespaced format `project-slug/template-name`:

```bash
e2b sandbox spawn your-project-slug/<template-name>
```

The same naming format works in the SDKs. Pass `project-slug/template-name` as the template alias to `Sandbox.create()`.

## Unpublishing

To revoke public access, either toggle the template back to private in the [dashboard Templates tab](https://e2b.dev/dashboard?tab=templates), or run:

```bash
e2b template unpublish <template-name>
```

The template stays in your project and remains usable by your project. It is just no longer reachable by others.

For more on naming and how the project-slug prefix works, see [Template names](/docs/template/names).