✓Direct Answer

When you paste or drag images and documents into Oyma, they are saved directly into your vault's local attachments folder. Notes reference them using standard Markdown image links, ensuring complete portability.

Transparent Asset Storage Without Database Obfuscation

Many note-taking platforms store pasted screenshots and uploaded PDF attachments in hidden binary database blobs or on external cloud content delivery networks (CDNs). If you disconnect from the internet or cancel your subscription, those images fail to load or are lost entirely.

In Oyma, all media attachments are stored as plain files directly inside your local vault folder.

How Attachments Are Handled

When you paste an image from your clipboard (⌘V) or drag a PDF into the editor:

  1. Local File Generation: Oyma writes the binary asset into your designated attachments folder (for example, assets/ or attachments/).
  2. Deterministic Naming: Files are named using a timestamp or document-relative hash (e.g., Pasted-image-20261009-143022.png).
  3. Standard Markdown Syntax: The editor inserts a standard CommonMark or Obsidian-style link: 
    ![System Architecture Diagram](assets/Pasted-image-20261009-143022.png)

Attachment Location Preferences

In Preferences > Files & Links, you can choose how attachments are stored:

  • Root Assets Folder: Save all attachments in a single top-level assets/ directory.
  • Subfolder Under Current Note: Store attachments in an assets/ folder alongside the parent document.
  • Same Folder as Note: Keep images in the exact same directory as the .md file.
+-----------------------------------------------------------+
| Vault Attachment Configuration                            |
|                                                           |
| Attachment Storage Mode: [Dedicated assets/ directory ▼] |
| Automatic Compression:   [Compress high-res PNG to WebP]  |
| Max Asset Size Warning:  [50 MB]                          |
+-----------------------------------------------------------+

Because all links use standard relative filesystem paths, opening your notes in any other CommonMark viewer will render images and diagrams perfectly without broken asset links.

Media Asset Integrity and Portability

Managing attachments cleanly inside your vault:

  • Designated Assets Directory: Store pasted images and dropped PDFs in a tidy attachments/ folder on disk.
  • Standard Markdown Syntax: Assets are referenced using standard relative paths (![Diagram](attachments/image.png)), ensuring compatibility across any CommonMark editor.
  • Retina Image Scaling: High-resolution screenshots render crisply while preserving natural layout proportions.
  • Zero Database Blobs: Attachments remain standalone files on disk, making them easy to inspect, backup, and edit externally.

Open Asset Storage and Relative Linking

Screenshots, PDFs, and media attachments reside as standard files in your vault’s attachments/ folder. Standard relative Markdown links ensure images render properly across any CommonMark viewer.

You can drag assets from your vault folder into emails, presentation slides, or other desktop applications without needing to export or extract them from a database container.

Attachment Storage Invariants

  • Designated Folder: Pasted media saves directly into your vault’s attachments/ folder.
  • Open Standards: Images and PDFs are stored as clean PNG, JPEG, and PDF files on disk.
  • Relative Paths: Links use standard Markdown syntax (![Title](attachments/file.png)) for total portability.
  • Zero Blobs: Zero proprietary database packaging; files are directly accessible in Finder.

Related Questions & Architecture Guides