# Debugging Projects

### Debugging Tools

todo

### Web Profiler

So long as you are running a debug build / using an appmanifest which does not strip profiling, you you use the web profiler to inspect your running project. This is done simply by running the project and going to <http://localhost:8001/> in your browser. (**todo** test with other non-localhost targets)

You will see a page where you can capture frame data from the engine. You can also inspect the sizes of all resources currently being used in your project.&#x20;

Clicking the **Capture** button to get data from a fresh frame.

By using the web profiler, you can get a clue as to what is taking the most processing during each frame. If your game is running slow this is where you can go to see why. The example images below are for an empty project.

![](/files/-LKNKFPM0ydwz9DAwiAP)

![](/files/-LKNKIXgVHP5QftunpKw)

**todo** explain all of the options in the list.


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://read.bookofdefold.com/defold-a-z/debugging-projects.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.