> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/web/get-started/faq/custom-stamp-appearance.md).

# Why does a custom Stamp annotation lose its appearance after being resized?

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

Custom Stamp annotations rely on both an **appearance** and the original **image data**. The appearance is a rendered snapshot of how the stamp currently looks, while the image data is the original source image used to create that appearance. When a stamp is first loaded, WebViewer can display it using the appearance alone.

When a custom Stamp annotation is resized, moved, or otherwise modified, the existing appearance is discarded and a new appearance must be generated to reflect the updated annotation state. To regenerate the appearance, WebViewer needs access to the original image data. If the image data is unavailable, WebViewer cannot regenerate the appearance, causing the stamp image to disappear.

To prevent this issue, ensure that the stamp's image data is preserved when exporting and importing annotations. If the XFDF does not contain `<imagedata>`, the image can be restored after import by calling `annotation.setImageData(...)` before the annotation is edited. This allows WebViewer to regenerate the appearance whenever the annotation is updated.


---

# 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.apryse.com/web/get-started/faq/custom-stamp-appearance.md?ask=<question>&goal=<user_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.