DagerottDev191 downloadsSync public YouTube playlists into notes with metadata, transcripts, mobile support, and optional AI summaries.
An Obsidian plugin that automatically syncs public YouTube playlists into notes with the same metadata as YT Knowledge Notes (title, channel, URLs, IDs, thumbnail, description, upload date, category, duration, keywords) plus a transcript. YouTube syncing requires no YouTube API key. Optional AI summaries can use OpenAI, NVIDIA NIM, or another OpenAI-compatible endpoint chosen by the user.
The plugin supports Obsidian on desktop, iOS, iPadOS, and Android.
YouTube/<Playlist Name>/._Index.md per playlist (table of all videos) and a root Index.md.




Install YouTube Playlist Sync directly from the Obsidian Community Plugins directory, then enable it.
.obsidian/plugins/ (create it if missing).youtube-playlist-sync inside it.main.js and manifest.json from the latest release into it.https://www.youtube.com/playlist?list=PL...) and click Add. Repeat for as many
playlists as you want.The first sync creates all video notes; later syncs only add new ones.
| Setting | Default | What it does |
|---|---|---|
| Playlists | — | Public YouTube playlist URLs to sync |
| Sync when Obsidian opens | on | Run a sync shortly after Obsidian starts |
| Sync interval (minutes) | 30 | Re-sync every N minutes while active; 0 disables |
| Base folder | YouTube |
Vault folder where playlists are written |
| Create index notes | on | Per-playlist _Index.md + root Index.md |
| Transcript format | readable | Readable paragraphs or timestamped lines |
| Preferred caption language | (empty) | e.g. en; empty = first available transcript |
| Media embed | video | Embed the YouTube player, thumbnail, or nothing |
| Tags | youtube |
Extra tags added to every generated note |
| Video frontmatter template | built-in metadata template | Customize properties for newly generated video notes |
| Enable AI summaries | off | Enables optional AI summary features |
| AI provider | OpenAI | OpenAI, NVIDIA NIM, or Custom OpenAI-compatible endpoint |
| API key | — | Secret selected from Obsidian SecretStorage; optional for unauthenticated custom/local endpoints |
| API base URL | provider default | Endpoint base URL, normally ending in /v1 |
| API protocol | provider default | Responses API or Chat Completions |
| Model ID | provider default | Any model ID available from the configured endpoint |
| AI prompt mode | default | Use, append to, or replace the built-in summarization guidance |
| Custom AI instructions | (empty) | Optional focus, tone, and detail instructions |
| Generate summaries automatically | on | When AI is enabled, summarize new notes after they are created |
AI is completely optional. YouTube playlist syncing, metadata, transcripts, and note creation continue to work without any AI provider.
To enable AI summaries:
The OpenAI preset uses:
https://api.openai.com/v1gpt-5.6-lunaThe model ID and endpoint remain editable.
ChatGPT subscription OAuth is not used. OpenAI currently does not expose a supported public flow that lets an arbitrary third-party Obsidian plugin consume OpenAI API models against a user's ChatGPT plan. The plugin therefore uses a user-supplied API key today. Its internal auth type is designed so a supported OAuth token flow can be added later without rewriting the AI summary engine.
The NVIDIA NIM preset uses:
https://integrate.api.nvidia.com/v1openai/gpt-oss-20bReplace the starter model with any model ID available to your NVIDIA endpoint. NVIDIA NIM is OpenAI-compatible, so the same summary provider can be reused with a NIM API key.
Choose Custom OpenAI-compatible endpoint to use another service or your own server. Configure:
This can work with compatible hosted providers or self-hosted servers such as NIM/vLLM-style endpoints. A trusted local endpoint that requires no authentication may leave the secret unset. Compatibility depends on the endpoint implementing the selected OpenAI-style API.
Security: the selected credential is sent as a Bearer token to the configured base URL. Only configure endpoints you trust. Switching provider presets clears the selected secret to reduce the chance of accidentally sending one provider's key to another provider.
Commands:
Automatic AI generation happens only after the YouTube note is successfully created. An AI-provider error therefore never causes the underlying playlist sync or note creation to fail.
For very long transcripts, the plugin summarizes transcript chunks first and then produces one final coherent summary.
The AI prompt mode setting has three choices:
The fixed JSON response contract is always retained so the five rendered summary sections stay reliable. The video title, channel, and transcript are supplied separately; custom instructions should describe the desired focus, tone, or level of detail. Clear the instructions and switch back to Default guidance to restore the original behavior.
Every video note has YAML frontmatter with the same core property set ytkn uses:
title, aliases, source, channel, channelUrl, channelId, videoUrl, videoId,
playlistUrl, playlistId, thumbnailUrl, videoDescription, uploadDate, videoCategory,
durationSeconds, keywords, generated, plus your tags.
When an AI summary is generated, the plugin also records aiSummary, aiProvider, aiModel,
and aiGenerated. The AI content is wrapped in internal markers so regeneration can safely
replace that block without touching your other edits.
The Video frontmatter template setting accepts YAML without the opening and closing ---
lines. Values are inserted with placeholders:
title, aliases, source, channel, channelUrl, channelId, videoUrl, videoId,
playlistUrl, playlistId, thumbnailUrl, videoDescription, uploadDate, videoCategory,
durationSeconds, keywords, generated, tags, aiSummary, aiProvider, aiModel, and
aiGenerated.
For example:
title: {{title}}
source: youtube
videoId: {{videoId}}
url: {{videoUrl}}
creator: {{channel}}
topics: {{tags}}
Placeholder values are YAML-encoded. If an optional value is unavailable, its entire template
line is omitted. source: youtube and a non-empty videoId are required so the plugin can
recognize notes and avoid duplicates. Use Validate and save before syncing, Preview to
inspect sample output, or Reset default to restore all standard properties.
Template changes affect new notes only. To update existing generated video notes, run Apply frontmatter template to existing YouTube notes from the command palette or plugin settings. The migration shows a sample and note counts before confirmation, preserves note bodies and unknown user properties, and reports changed, unchanged, skipped, and failed notes. YAML comments and formatting may be normalized. Playlist and root index notes are never migrated.
The plugin supports iOS/iPadOS and Android using Obsidian's cross-platform Vault and HTTP APIs. Mobile operating systems may suspend Obsidian when it is in the background, so the plugin does not claim background execution while the app is closed or suspended.
Supported mobile behavior:
If a mobile sync is interrupted, already-created notes are detected on the next run and skipped, so syncing resumes with the remaining videos.
For normal playlist syncing, the plugin makes outbound HTTPS requests to YouTube to fetch playlist data, video metadata, thumbnails, and captions for the public playlists you configure. It does not collect telemetry.
When AI summaries are disabled, no vault content is sent to an AI service.
When AI summaries are enabled, the plugin sends only the generated video's title, channel,
transcript, and configured summary instructions to the AI endpoint you configured. Other vault
notes and unrelated vault content are not sent. API keys are referenced through Obsidian
SecretStorage rather than stored in the plugin's data.json.
The hidden metadata marker used for repeatable frontmatter migrations contains video and playlist metadata plus AI provider/model status. It never contains transcripts, summary text, credentials, or API keys.
npm install
npm run typecheck # type check only
npm test # unit tests
npm run check # type check + unit tests
npm run build # type check + bundle main.js
node test/smoke.mjs <playlistId> # end-to-end check of the YouTube fetch layer
The YouTube fetch layer lives in src/youtube.ts, note rendering in src/noteRenderer.ts, sync
orchestration in src/main.ts, and AI integration in src/ai/.
If this plugin saves you time, you can support its development: