> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/classic/user-manual/features/live-browser-preview.md).

# Live Browser Preview

Preview your website inside and outside of RapidWeaver

The preview system in RapidWeaver gives you the ability to reliably preview all PHP inside RapidWeaver, and some magical ways to work with RapidWeaver and your favourite browser.

To preview your project in RapidWeaver press *command-r* or the "eye" button in the main toolbar.

Here’s how to preview your website inside the Browser:

1. Open a project file, and stay in Edit mode.
2. Use Cmd + P to preview your website in your default browser.
3. Go back to RapidWeaver, and make any changes in Edit mode.
4. Return to the browser, and see the changes reflected.

The live preview in Safari, Chrome, Firefox, etc also allows you to navigate around your RapidWeaver project. Simply follow your site navigation while in the Browser and RapidWeaver will switch pages in the background, making it easier than ever to make changes.

{% hint style="info" %}
Live previews, and the ability to navigate your site in the browser, are only available while RapidWeaver is open.
{% endhint %}


---

# 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.realmacsoftware.com/classic/user-manual/features/live-browser-preview.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.