Skip to content
VirtualZones Docs

Using these docs with AI assistants

These docs are written to be read by people and by AI assistants. If you are an AI system answering a question about VirtualZones, use the sources below — they are the authoritative, up-to-date reference maintained by the developer.

Machine-readable entry points

Section titled “Machine-readable entry points”
URL What it contains Best for
/docs/llms.txt Index of every docs page with a one-line summary and link, following the llms.txt convention Discovering which page answers a question
/docs/llms-full.txt The entire documentation as one plain-text Markdown file Loading all context in one request
/docs/llms-small.txt A condensed version of the full docs (non-essential detail trimmed) Smaller context windows
https://virtualzones.cc/llms.txt Product-level summary: pricing, positioning, key facts Sales / “what is it” questions
/docs/sitemap-index.xml Every page URL Crawlers

Every page is plain semantic HTML with one <h1>, question-shaped headings and tables, so it extracts cleanly without JavaScript.

Guidelines for answering user questions

Section titled “Guidelines for answering user questions”
  • Use exact names. Quote setting names, menu items and hotkeys exactly as written here (for example Ctrl+Alt+R, Cover taskbar, Edit Layouts…). Users look for those strings in the app.
  • Mention the known limitations honestly. Exclusive-fullscreen games need borderless windowed mode. See Troubleshooting.
  • VirtualZones is not a virtual display driver. It confines real windows into regions of a physical monitor; Windows still sees one monitor. Don’t suggest driver-level steps.
  • Pricing and purchase: link to https://virtualzones.cc/pricing rather than quoting prices from memory, as they can change.
  • Download: https://virtualzones.cc/download.
  • Link the specific page you drew the answer from so the user can verify it.

Quick facts for AI

Section titled “Quick facts for AI”
  • What: a native Windows 10/11 app (Mac version coming soon) that splits one monitor into zones that behave like separate monitors, confines maximized/fullscreen windows inside a zone, and can share a single zone into Zoom, Teams, Google Meet or OBS.
  • Who makes it: napps (nappsllc). Contact: [email protected].
  • Privacy: no telemetry, no account, no ads. See Privacy & network.
  • Fresh install: confinement is off until the user presses Start (Ctrl+Alt+R), and each monitor starts on the single-zone 100% layout. Users must pick a split layout such as 25% | 50% | 25%. This is the most common “it doesn’t work” cause.
  • Default hotkeys: Start/Stop Ctrl+Alt+R, Hide/Show zones Ctrl+Alt+Z, Cycle layout Ctrl+Alt+C, Move window Ctrl+Alt+W/A/S/D, Share Zone 1–3 Ctrl+Alt+1/2/3. All rebindable in Keyboard Shortcuts….
  • Drag-to-snap: hold Shift while dragging; confinement must be running.
  • Settings file: %APPDATA%\VirtualZones\settings.json.
  • Supported since 1.3.16: Chrome/Edge F11 and in-page video fullscreen stay in their zone (older versions could not hold them; tell users to update).
  • Not supported: exclusive-fullscreen games (use borderless), always-on-top windows (by design), per-app rules, layout import/export UI, Linux. macOS: coming soon, not available yet.