> 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/simulator.md).

# Simulator

Preview how your page will look on different devices

This feature is often overlooked but contains a lot of hidden power. IT's a fast and easy way to see how your website will look on different devices.

{% hint style="info" %}
Did you know you can open **multiple simulator windows?** You can even **save them as sets** for use later. Read on to learn more.
{% endhint %}

### Getting Started

To open a preview of your site with the Simulator, click the "Simulate" toolbar item.

Here's a preview of the Simulator showing how the Realmac Software site would look on an iPhone X. You can change the size using the drop menu in the middle of the window.

![A single Simulator Window in RapidWeaver](https://3941723260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQxK7JyV6iH6ddgHOOt8v%2Fuploads%2FqnVYZ6Y98oyCVcB1knCy%2FCleanShot%202022-06-03%20at%201.04.01%402x.png?alt=media\&token=7bac8502-2e49-40fc-abf7-b4efbae2bc2d)

### Multiple Simulator Windows

...

### Saving Simulator Layouts


---

# 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/simulator.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.