# Renaming Image fails

**URL:** <https://community.bear.app/t/renaming-image-fails/19692>\
**Category:** Lettera feedback\
**Tags:** bug\
**Created:** [August 5, 2026, 12:56am UTC](https://community.bear.app/t/renaming-image-fails/19692 "2026-08-05T00:56:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tpw](https://avatars.discourse-cdn.com/v4/letter/t/eb9ed0/32.png) [@tpw](https://community.bear.app/u/tpw)\
**Post date:** [August 5, 2026, 12:56am UTC](https://community.bear.app/t/renaming-image-fails/19692/1 "2026-08-05T00:56:15Z")

</div>

This template is for bug report only:

- **Lettera Version** : 1.0.0 (4178)
- **macOS Version** : 26.5.2
- **What were you doing** : renaming a photo
- **What feature did you use** : rt-click on photo, select “rename” menu item
- **What happened** : name appeared to change via the dialog box but didn’t really change
- **What did you expect to happen** : expected the file on disk to be renamed

Besides adding existing image files to the MD file I also copy-paste images from other sources and Lettera will create a physical file in the same folder as the MD file which is what I expected. However, since those filenames are just incremented numbers, they are meaningless and I am trying to rename them to be meaningful when I look at the file system.

thanks

-tom

---

<div class="post-metadata">

**Author:** ![tpw](https://avatars.discourse-cdn.com/v4/letter/t/eb9ed0/32.png) [@tpw](https://community.bear.app/u/tpw)\
**Post date:** [September 28, 2026, 6:14pm UTC](https://community.bear.app/t/renaming-image-fails/19692/2 "2026-09-28T18:14:52Z")

</div>

@trix180

This is still broken in Version 1.0.0 (4458).

-tom

---

<div class="post-metadata">

**Author:** ![trix180](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/trix180/32/588_2.png) [@trix180](https://community.bear.app/u/trix180)\
**Post date:** [September 30, 2026, 3:14pm UTC](https://community.bear.app/t/renaming-image-fails/19692/3 "2026-09-30T15:14:23Z")

</div>

Thanks. We’ll look into this as soon as possible.
