Feature Request: Custom Attachment Folder for Pasted Images

Hi Lettera team,

I’d like to suggest an option for configuring where pasted images are stored.

Currently, when I paste an image directly from the clipboard into a Markdown file, Lettera saves the image in the same directory as the Markdown file. This works, but for larger Markdown folders it can quickly make the directory cluttered with image files.

Apps such as Obsidian and Cogito allow users to specify a dedicated attachment folder relative to the current Markdown file, for example:


article.md
Attachments/
  image-1.png
  image-2.png

Then the Markdown could reference the image with something like:


![](Attachments/image-1.png)

It would be great if Lettera could provide a setting such as Attachment Folder or Default Attachment Path, where users could specify a relative folder like:


Attachments

or


.attachments

When an image is pasted from the clipboard, Lettera could automatically create the folder if needed and save the image there.

I think this would make image-heavy Markdown documents much easier to organize, especially when using folders as workspaces.

Thanks for considering it!

2 Likes

Second this. Would be amazing.

I agree. Would love to see something like this.

Yes, I’m aware of TextBundle, and I’ve seen some previous discussions about it in the community.

What I’m hoping for is a more seamless workflow for regular Markdown files: when I paste an image, it would automatically be stored in a dedicated attachment folder without requiring any extra steps.

Right now, pasted images are saved directly alongside the Markdown file. Once there are several notes and images in the same folder, opening it in Finder quickly becomes quite messy.

Ideally, I’d like to keep using normal .md files while having pasted images automatically organized into a configurable subfolder such as assets/ or attachments/.

As a side note, I also prefer keeping the document itself as a regular .md file because it’s much easier to share. If I send someone an .md file, they can usually at least open it and get a rough idea of the content. With a .textbundle, there’s a much higher chance they’ll just get a “no application is available to open this file” type of message instead.

1 Like

Default folders for storing assets are on our list, so it’ll get there eventually :slight_smile:

1 Like

Great to hear! Do you have a rough timeline for when this feature might be available?