> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-downloads/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/os-downloads/resources/product-resources/getting-started-with-geopackage-and-vector-tiles-guides/getting-started-with-vector-tiles/using-os-styles-on-vector-tiles-you-have-created.md).
# Using OS styles on vector tiles you have created
It is possible to use OS styles on vector tiles you have created. The following step-by-step instructions outline how to do this:
1. Download and unzip the appropriate OS product folder of stylesheets from [GitHub](https://github.com/OrdnanceSurvey), for example, [OS's OS-Open-Zoomstack-Stylesheets repository](https://github.com/OrdnanceSurvey/OS-Open-Zoomstack-Stylesheets) [on GitHub](https://github.com/OrdnanceSurvey/OS-Open-Zoomstack-Stylesheets).
2. Once you have downloaded and unzipped the folder of stylesheets, navigate to *Vector Tiles* > *Mapbox GL Styles*.
3. If appropriate, choose the style you want to use and open the .json file (for example, OS Outdoor.json) in a text editor.
4. Find the following piece of code near the top of the file and enter your data source URL where it says ADD–SOURCE–URL–HERE:
Screenshot of the sources section of the .json file showing where the user can add the source URL
{% hint style="info" %}
*You can find* [*more information on the different source types*](https://docs.mapbox.com/mapbox-gl-js/style-spec/sources/) *on Mapbox's documentation site*
{% endhint %}
5. Save the .json file.
The style is now ready to use. You can customise the style if you want to (for example, you could adapt the style of a map to match your own brand colours). [Maputnik](https://maputnik.github.io/) is a good open-source map editor tool for creating and customising vector tile styles.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.os.uk/os-downloads/resources/product-resources/getting-started-with-geopackage-and-vector-tiles-guides/getting-started-with-vector-tiles/using-os-styles-on-vector-tiles-you-have-created.md?ask=&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 `automate deployments from our CI pipeline` 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.
