> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pdfm-ug/parallels-desktop-for-mac-27-users-guide/use-windows-on-your-mac/setting-how-windows-works-with-macos/setting-windows-to-appear-in-a-single-window/monitoring-windows-in-a-scalable-window.md).

# Monitoring Windows in a Scalable Window

You can set Windows to appear in a window that can be resized to any size so that the content scales in size with the window. This is called **Picture in Picture** mode. This mode can be useful if you want to monitor applications and other tasks running in Windows as you work in macOS.

To switch to Picture in Picture mode:

* From Window mode, choose **View** > **Enter Picture in Picture**.

For more information on Picture in Picture mode, see [the Picture in Picture mode settings topic](/landing/pdfm-ug/parallels-desktop-for-mac-27-users-guide/advanced-topics/picture-in-picture-mode.md).


---

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

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

```
GET https://docs.parallels.com/landing/pdfm-ug/parallels-desktop-for-mac-27-users-guide/use-windows-on-your-mac/setting-how-windows-works-with-macos/setting-windows-to-appear-in-a-single-window/monitoring-windows-in-a-scalable-window.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 `build a script that syncs our docs to a CMS` 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.