Item logo image for Threads Clipper for Obsidian

Threads Clipper for Obsidian

ExtensionTools13 users
Item media 5 (screenshot) for Threads Clipper for Obsidian
Item media 1 (screenshot) for Threads Clipper for Obsidian
Item media 2 (screenshot) for Threads Clipper for Obsidian
Item media 3 (screenshot) for Threads Clipper for Obsidian
Item media 4 (screenshot) for Threads Clipper for Obsidian
Item media 5 (screenshot) for Threads Clipper for Obsidian
Item media 1 (screenshot) for Threads Clipper for Obsidian
Item media 1 (screenshot) for Threads Clipper for Obsidian
Item media 2 (screenshot) for Threads Clipper for Obsidian
Item media 3 (screenshot) for Threads Clipper for Obsidian
Item media 4 (screenshot) for Threads Clipper for Obsidian
Item media 5 (screenshot) for Threads Clipper for Obsidian

Overview

Save Threads posts to Obsidian via Local REST API or Obsidian URI

Threads Clipper for Obsidian saves the Threads posts you care about into your Obsidian vault as structured Markdown notes — the moment you tap Like or Bookmark on threads.net or threads.com. No copy-paste, no manual formatting. WHAT IT DOES šŸ’¾ Auto-save on Like/Bookmark — no extra click. Tap ā™” or the bookmark button and the post becomes a note in your vault. šŸ“ Clean Markdown with YAML frontmatter — author, post URL, timestamp, tags, topic, comment count, and thread length are stored as Obsidian properties so your note is fully searchable and graph-aware. 🧵 Threads, reposts, quotes, carousels — multi-post threads keep their chained-post order; reposts and quotes are clearly marked in the frontmatter. šŸ–¼ļø Image handling — keep the original CDN URL inline, or download images locally to your vault (REST mode only). šŸ’¬ Comment collection (optional) — pull replies under a post into a dedicated section, with filters for author-only replies and minimum length. šŸ¤– AI transformation (optional) — turn each post into a structured study note (executive summary, key concepts, detailed analysis, action items, Feynman explanation) using your own API key. 🌐 English / ķ•œźµ­ģ–“ UI — auto-detected from your browser or switched on demand from the options page. Default prompt template follows the same language. TWO SAVE METHODS • Obsidian URI (default, no plugin required) Notes are created via the obsidian://new URI through the clipboard and saved to the last active Obsidian vault. Easiest setup. Images stay as URL references. • Local REST API Requires the Obsidian Local REST API community plugin. Enables direct vault writes, local image download, and richer error reporting. Switch between modes anytime in the options page. āš ļø IMPORTANT — PREFER THE POST DETAIL PAGE The Threads feed only renders the top-level post DOM, so chained thread items and reader comments are NOT available from the feed view. To capture the full thread plus replies into a single note: 1. Click into the post to open its detail page (URL pattern: /post/...). 2. Like ā™” or bookmark from there. 3. The extension captures every chained post in the thread and, if comment collection is enabled, the visible replies. Liking or bookmarking directly from the feed still works — the main post is saved correctly — but the rest of the thread and the discussion will be missing. For best results, open the detail page first. AI TRANSFORMATION (OPTIONAL) Off by default. When you enable it and configure a provider with your own API key, each saved note is transformed into a structured study format: 1. Executive Summary 2. Key Concepts (table) 3. Detailed Notes 4. Action Items 5. Feynman Explanation 6. Original post text (preserved at the bottom) Supported providers: OpenAI, Google Gemini, Anthropic Claude, xAI Grok, Z.AI GLM, and any OpenAI-compatible Custom/Local endpoint such as Ollama or LM Studio (API key optional for local endpoints). The transformation prompt template is fully editable. PRIVACY • All data — API keys, settings, statistics — is stored locally in Chrome storage. Nothing leaves your machine except: – Calls to your Obsidian REST plugin on localhost, or use of the local clipboard for URI mode. – Calls to the AI provider you configured, only when AI transformation is on, and only with the API key you supplied. • No analytics, no telemetry, no third-party trackers. • The extension only activates on threads.net and threads.com. REQUIREMENTS • Chrome 116 or newer. • An Obsidian vault on your machine. • (REST mode only) The Obsidian Local REST API community plugin, enabled and running. • (AI mode only) An API key from your chosen provider. SUPPORT Issues, feature requests, and source code: https://github.com/starhunt/threads-clipper-for-obsidian

Details

  • Version
    1.5.7
  • Updated
    June 4, 2026
  • Offered by
    starhunt
  • Size
    69.46KiB
  • Languages
    2 languages
  • Developer
    Email
    starhunt@gmail.com
  • Non-trader
    This developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.

Privacy

Manage extensions and learn how they're being used in your organization

Threads Clipper for Obsidian has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.

Threads Clipper for Obsidian handles the following:

Authentication information
Website content

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Support

For help with questions, suggestions, or problems, visit the developer's support site

Google apps