> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/documentation/features/user-interface/large-view-annotation-text.md).
# Large View: Annotation – Text
## Large View
* Access the large view of an image by clicking on its thumbnail.
## Editing mode
* Access the **editing** mode by clicking on the **edit** icon.
## Add text
* Add text to an image by selecting the **text icon.**
* Enter the desired content inside text box.
* The text is now displayed on the image.
* The text can be:
* **moved**
* **rotated**
* **resized**
by using the handle.
## Change text
* The text content can be modified by double-clicking on it.
## Change text color
* Select the desired color from the color-palette by clicking on it as shown below.
* The text is now colored as previously selected.
## Delete text
* A text can be deleted from the image by clicking on the eraser icon and then click the text you want to delete.
* Text is now removed.
---
# 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.sharinpix.com/documentation/features/user-interface/large-view-annotation-text.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.
