> For the complete documentation index, see [llms.txt](https://docs.firecal.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.firecal.app/my-certs/replace-an-attachment.md).
# Replace an Attachment
Swap in a better copy.
Uploaded a blurry photo, or found a cleaner digital copy of the same Cert? Replace the attachment without touching anything else.
## Tap to Open
When looking at your Locker, **Tap a Cert** to open it.
## Tap Replace
Tap **Replace**, right under the document preview. On a phone or tablet, choose **Take Photo**, **Choose from Photos**, or **Choose from Files**, and on the web, pick a file from your computer.
When the upload finishes, you'll see **Attachment replaced. Previous version moved to history.** and the new document will appear in the preview. Your dates, renewal progress, and applied training all stay exactly as they were.
{% hint style="info" %}
**Renewed your Cert? Use Renew instead.** Replace is for a better copy of the *same* Cert. When you've actually renewed, tap **Renew** so CertLocker can start a new renewal cycle and keep a record of the old one (see [Renew a Cert](/my-certs/renew-a-cert.md)).
{% endhint %}
## No Attachment Yet?
If a Cert doesn't have a document, you'll see **Upload attachment** in place of the preview. Tap it, and choose your file the same way.
---
# 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.firecal.app/my-certs/replace-an-attachment.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.
