---
title: "Portals"
source: "https://browserpod.io/docs/understanding-browserpod/portals"
---

# Portals

How Portals let you preview and share services running inside a Pod

A **Portal** is a BrowserPod networking feature that gives a service running inside a [Pod](https://browserpod.io/docs/reference/BrowserPod.md) its own URL, so you can preview it and share it with others.

Portals are part of [BrowserPod Edge](https://browserpod.io/docs/understanding-browserpod/api-key.md) (free tier available): they need a Pod booted on the [Edge network](https://browserpod.io/docs/understanding-browserpod/networking.md) with an API key. When a Pod on the Edge network starts listening on a port, BrowserPod automatically creates a URL that forwards traffic to that server.

## What Portals enable

Portals let you:

- **Preview your app**: Show a server running in the Pod on your own page, for example in an iframe.
- **Share it**: Send the URL to teammates so they can open the running app without deploying it.
- **Build demos**: Let users try a working app inside docs or product tours.
- **Test on other devices**: Open the URL on your phone to test a server running in your laptop’s browser.

## How Portals work

- A Portal is not a separate server. The server runs inside the Pod, in the browser, and the Portal forwards traffic to it.
- Each port a server listens on gets its own Portal. [`onPortal`](https://browserpod.io/docs/reference/BrowserPod/onPortal.md) gives you its `url` and `port`.
- The URL is randomly generated, but anyone who has it can reach the server.
- A Portal only works while the page running the Pod is open, and its URL changes every time the Pod boots.

If you want the setup steps or code examples, see [Set up a Portal](https://browserpod.io/docs/guides/setup-portal.md).
