> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/web-browser/loading-embedded-pages.md).

# Loading embedded pages

This guide assumes you've followed [Setup the browser widget](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/web-browser/setup-the-browser-widget.md).

You can load webpages into your browser, where the content is packaged into the game.

{% hint style="info" %}
You must place content inside a folder called `WebUI` for it to be packaged correctly.
{% endhint %}

### Create the HTML page

Create a folder in your project's content folder called `WebUI` .

<figure><img src="https://970394512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft3SBfOIsRz4GCNFFpae7%2Fuploads%2Fgit-blob-bc1c34e951aae24fa24a4e3d25e1d9cc94d0d332%2Fimage%20(1504).png?alt=media" alt=""><figcaption><p>The WebUI folder.</p></figcaption></figure>

Open this folder in the Windows Explorer and create a file inside called `index.html`.

Paste this text in the file:

```html
<!DOCTYPE html>
<html lang="en">
<head>
    <style>
        @import url('https://fonts.googleapis.com/css2?family=Roboto:wght@400&display=swap');
        body {
            display: flex;
            justify-content: center;
            align-items: center;
            height: 100vh;
            font-family: 'Roboto', sans-serif;
            font-size: 4rem;
            background: #ffffff;
        }
    </style>
</head>
<body>
    Hello World!
</body>
</html>
```

### Load the HTML page into the browser

Add the following node to your browser widget blueprint on `Event Construct`:

{% @blueprintue-embed/embed url="<https://nextjs-boilerplate-jl63.vercel.app/b91f9fe8-63df-4135-8d82-2f46f0fdb81f>" %}

Once you load in with PIE you should see the page loaded in your browser, for example in 3D space by following [In-world browser](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/web-browser/in-world-browser.md):

<figure><img src="https://970394512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft3SBfOIsRz4GCNFFpae7%2Fuploads%2Fgit-blob-2aaafa9f677c494449196f9a3a7bc655b562f50f%2Fimage%20(1511).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/web-browser/loading-embedded-pages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
