---
title: "Rename a media asset without replacing its content"
description: "Verify that changing an asset display name updates the library and detail view while its stable identity and prepared source content stay consistent."
canonical_url: "https://vostride.com/agent-library/files-media/rename-preserves-asset.md"
md_url: "https://vostride.com/agent-library/files-media/rename-preserves-asset.md"
content_kind: "recipe"
topic: "files-media"
---

# Rename a media asset without replacing its content

Verify that changing an asset display name updates the library and detail view while its stable identity and prepared source content stay consistent.

## Risk

Rename operations can accidentally create a duplicate asset or update only local display state. A stable identifier and a recognizable preview provide separate checks of identity and presentation.

## Fixtures

- A test library contains an app-resident image called Old campaign banner with a distinctive purple diagonal stripe.
- The fixture manifest records its immutable asset identifier and source checksum for a prepared read-only verification hook.
- The intended replacement name is New campaign banner, and no existing asset uses that exact name.

## Steps

1. Open Old campaign banner and verify the purple-stripe preview and current asset identifier.
2. Use Rename, enter New campaign banner, save, and verify the detail title updates.
3. Return to the library and verify one renamed item appears while the old name is absent.
4. Reload the renamed detail and verify the same purple-stripe content and immutable identifier remain.
5. Run the prepared read-only asset check and verify the source checksum is unchanged and no second asset was created.

## Expected results

- The immutable identifier before and after rename is identical.
- The stored display name persists as New campaign banner after reload.
- The independent source checksum and asset count confirm rename did not replace bytes or duplicate the object.

## False-pass traps

- A visually similar preview cannot prove byte preservation; that claim needs the prepared checksum evidence.
- Finding the new title without looking for the old title can miss an accidental copy operation.

## Cleanup

- Restore the original display name if the fixture is reusable, or delete the test asset by identifier.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa web testing](/docs/agent-qa/guides/web-testing.md)

- [Files and media QA recipes](/agent-library/files-media.md)
- [Software factory QA library](/agent-library.md)