> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/developer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/developer/creating-locations/testing-a-location-locally-on-windows.md).

# Testing a location locally on Windows

You can create a location in the ENGAGE SDK, and then test it in the ENGAGE app. However, the location is restricted to your development machine, and you can't invite other ENGAGE users to join your location.

To test a location locally on a Windows OS machine, follow the steps described in [Building a location bundle](/developer/creating-locations/building-a-location-bundle.md) and select the **Build for Windows** check box. Then, to access the location in the ENGAGE app, complete the following steps:

1. Open the ENGAGE app, and then log in.
2. On the menu screen, press F10.
3. In the **Test Local Scene Bundle** window, select **BROWSE**.
4. Browse to you ENGAGE SDK folder, and then to `/AssetBundles/Windows`.
5. Select the `.engagebundle` file for the location that you want to test, and then select **Open**.
6. In the **Test Local Scene Bundle** window, for the location that you want to test, select **LOAD**.

The location loads in ENGAGE. You have the same functionality that you would have as a host in any ENGAGE Session.

{% hint style="info" %}
You can use the profiling tools in ENGAGE to analyse your location and identify any performance issues. For more information, see [Profiling](/developer/profiling.md).
{% endhint %}