Image Flow

pending

by chillcharlie357

A plugin that streamlines how images are pasted, stored, and uploaded.

★ 1 starsUpdated 3mo agoMITDiscovered via Obsidian Unofficial Plugins
View on GitHub

Obsidian Image Flow

Language: English | 中文文档

A plugin that streamlines how images are pasted, stored, and uploaded in Obsidian.

It listens to paste and drag‑and‑drop events in the editor, saves image files to your vault following configurable rules, and optionally uploads them via external CLI tools such as PicList.

Features

  • Automatic handling of pasted / dragged images

    • Intercepts editor paste and drop events, saves images into the vault and inserts links into the note.
    • Supports two link syntaxes:
      • Markdown: ![alt](path/to/image.png)
      • Obsidian wikilink: ![[image.png]]

  • Image renaming

    • Optional toggle to enable or disable automatic renaming.
    • Option to keep the original filename.
    • Custom rename pattern with a default of {date}-{time}-{random}.
    • Supported placeholders:
      • {date}, {time}, {timestamp}, {date:YYYYMMDD}, {random}, {filename}.

  • Save location rules

    • When upload is disabled, images are stored locally using flexible rules:
      • Vault Assets: always save to assets/
      • Current File Assets: save to {filename}.assets/
      • Current Folder Assets: save to {file_path}/assets/
      • Custom: arbitrary directory pattern with placeholders such as {vault}, {date}, {filename}, {file_path}.

  • Image upload (PicList / PicGo)

    • Optional upload flow that runs after the image is saved locally.
    • Built‑in strategy for piclist, picgo.
    • Image upload supports PicList as an uploader option: https://github.com/Kuingsmile/PicList.
    • Configurable command: use a bare command name or an absolute path.
    • Upload flow:
      • Execute the uploader CLI.
      • Extract the image URL from stdout / stderr or clipboard.
      • Replace the inserted image link with the remote URL.
    • Optional “delete local image after upload” toggle.

  • Upload profiles

    • Group upload‑related settings into reusable profiles.
    • Default profile is created automatically the first time upload is enabled.
    • Profile operations:
      • Rename the active profile.
      • Copy the active profile.
      • Delete the active profile (at least one profile is always kept).
    • Switching profiles automatically updates uploader type, command path, and the “delete local image after upload” flag.

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.