> 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/image-sync/sharinpix-transformations-examples.md).
# SharinPix Transformations Examples
This article demonstrates the different types of transformations that can be applied to an image in a SharinPix Album.
## Fill to Size
* Create an image with the exact given width and height while retaining the original aspect ratio. (height = width = 250 pixels)
## Fit to Size
* The image is resized so that it takes up as much space as possible within a bounding box defined by the given width and height values. (height = width = 250 pixels)
## Pad to Size
* Resize the image to fill the given width and height while retaining the original aspect ratio and with all of the original image visible. (height = width = 200 pixels)
## Scale to Size
* Change the size of the image exactly to the given width and height without necessarily retaining the original aspect ratio. (height = width = 150 pixels)
## Limit to size
* Limit the image's width and height to a specific value. If the image dimensions exceed the specified value(s), the image is down scaled to match the same. Else the image dimensions are retained. In the example below, the **Limit to size** value has been set to 250 pixels (height=width = 250 pixels) and the original image size is 300x300. Therefore, the image has been down scaled to a height and width of 250 pixels.
---
# 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/image-sync/sharinpix-transformations-examples.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.
