Ob-base: as image database

Feature requests
1

Use case or problem

When using Obsidian for knowledge management, images serve as crucial information carriers (such as screenshots, charts, and manuscripts) that need deep integration with text notes. However, Obsidian’s current image management is limited to basic attachment storage and insertion, lacking systematic classification, retrieval, and metadata management capabilities. Users need a tool to dynamically associate images with note content, enabling scenarios like:

  • Quickly retrieving specific images by tags, dates, or sources (e.g., “2025 conference record screenshots”);
  • Adding metadata to images, such as descriptions, copyright information, and linked note URLs;
  • Previewing images in a gallery format within database views and batch-managing properties via table views;
  • Automatically updating paths when cross-note referencing images to avoid file loss or broken links.

Existing image management tools (e.g., local folders, Eagle) are disconnected from Obsidian’s note system, making it difficult to form an organic whole between images and text content, thus reducing knowledge retrieval and reuse efficiency.

Proposed solution

Expand Obsidian’s Database feature into a core image management module with the following capabilities:

1. Image Database Creation and Metadata Management

  • Create a standalone “Image Library” database (e.g., .csv or .json format) in the Vault, allowing metadata fields for each image via YAML Frontmatter or table views:
    • Required fields: File name, storage path, list of notes containing the image, creation date;
    • Optional fields: Tags (supporting multi-tagging), descriptions, copyright information, source URLs, categories (e.g., “Diagrams,” “Screenshots”).

2. Visual Query and Gallery View

  • Add a Gallery View to Database interfaces, displaying images as thumbnails with hover previews of metadata (e.g., tags, descriptions).
  • Enable full-text search across image metadata and associated note content (e.g., searching “project timeline” to find both notes and linked charts).
  • Support filter/sort functions (e.g., filtering by tag “meeting” and sorting by “creation date descending”).

3. Dynamic Linking and Path Management

  • Automatically generate bidirectional links between images and notes (e.g., an image’s metadata shows all notes it is embedded in, while notes display a “Linked Images” section).
  • Implement a unified path management system: When moving/copying images within the Vault, auto-update all internal links to prevent broken references.

4. Batch Operations and Integration

  • Support bulk importing images with pre-filled metadata (e.g., via CSV templates).
  • Integrate with Obsidian’s existing features:
    • Embed database-generated image galleries directly into notes using a new ![[gallery:query]] syntax.
    • Sync metadata with external tools (e.g., EXIF data for photos, or PDF annotations) via plugins.

Current workaround (optional)

Users currently rely on:

  1. Manual folder organization (e.g., /images/year/month/), which lacks searchable metadata.
  2. Plugins like Image Toolkit for basic resizing, but no database-level management.
  3. External tools (e.g., Eagle, Notion) for image cataloging, with static links to Obsidian notes—prone to synchronization issues.
1 Like