> For the complete documentation index, see [llms.txt](https://docs.finops.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finops.softwareone.com/analysis/cost-map/view-cost-map.md).

# View Cost Map

The cost map enables you to visualize your cloud expenses by region/location and service, so you can detect areas with high spending across cloud providers. 

A cost map can also be used to view data transfer and connectivity costs.

### Viewing the cost map

To view the cost map: 

1. From the left sidebar, navigate to the **Cost map** page.
2. (Optional) Adjust the date range filter to view the data for a specific time period. 
3. Use the [Region cost map](/analysis/cost-map.md#region-cost-map) as follows to visualize your spending geographically across cloud deployments:
   * Hover over a circle to see detailed expense information. Use the **Show resources** link to open the **Resources** page, which displays all corresponding resources.
   * Toggle between the full-screen and regular window mode.
   * Use the **Summary by region** table to view details, such as expenses for your specified time period, the percentage of total expenses, and related cloud resources. 
4. Select the [Network traffic cost map](/analysis/cost-map.md#network-traffic-cost-map) to analyze costs associated with data transfer and connectivity.


---

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

```
GET https://docs.finops.softwareone.com/analysis/cost-map/view-cost-map.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.