Naver Blog Importer
pendingby hyungyunlim
Import posts from Naver Blog with AI-powered features, subscription management, and comprehensive content parsing
Naver Blog Importer (Obsidian Plugin)
Import Naver Blog and Cafe posts directly into your Obsidian vault with AI-powered enhancements.
Features
Blog Import
- Bulk Import: Import all posts from a blog by ID
- Single Post Import: Import individual posts by URL (desktop, mobile, m.naver.com)
- Subscription System: Subscribe to multiple blogs with auto-sync
Cafe Import (New!)
- Single Article Import: Import cafe articles by URL
- Private Cafe Support: Access private cafes with cookie authentication
- Organized by Cafe Name: Articles saved under cafe name subfolder
Common Features
- AI Features (optional): Auto-generate tags and excerpts using OpenAI, Anthropic, Google, or Ollama
- Image Download: Download and save images locally
- YouTube Embeds: Native Obsidian embed support for YouTube videos
- Duplicate Detection: Skip already imported posts
- Multi-language: Korean and English UI support
Installation
From Obsidian Community Plugins
- Open Obsidian Settings → Community Plugins
- Search for "Naver Blog Importer"
- Install and enable
Manual Installation
- Download latest release from GitHub
- Extract to
.obsidian/plugins/naver-blog-importer/ - Enable in Settings → Community Plugins
Usage
Blog Import
Bulk Import: Click ribbon icon → Enter blog ID → Import all posts
Single Post: Command palette → "Import single post" → Enter URL or LogNo
Supported URL formats:
https://blog.naver.com/blogid/lognohttps://m.blog.naver.com/PostView.naver?blogId=xxx&logNo=xxxhttps://m.naver.com/PostView.naver?blogId=xxx&logNo=xxx
Cafe Import
Single Article: Command palette → "Import cafe article" → Enter URL
Supported URL formats:
https://cafe.naver.com/cafename/articleidhttps://m.cafe.naver.com/cafename/articleid
Private Cafe Authentication
To access private cafes, you need to provide your Naver login cookies:
- Log in to Naver in your browser
- Open Developer Tools (F12) → Application → Cookies
- Find
NID_AUTandNID_SEScookie values - Enter them in plugin settings under "Naver Cafe Settings"
Output Format
Blog Post
---
title: "Post Title"
date: 2024-01-01
tags: ["tag1", "tag2"]
excerpt: "AI-generated summary..."
source: naver-blog
blogId: "example_blog"
url: "https://blog.naver.com/example_blog/123456789"
logNo: "123456789"
---
Post content with images, quotes, code blocks...
Posts are saved to: {defaultFolder}/{blogId}/{title}.md
Cafe Article
---
title: "Article Title"
date: 2024-01-01
author: "Writer Name"
articleId: "123456"
cafeId: "12345678"
cafeName: "Cafe Full Name"
cafeUrl: "cafename"
menuName: "Board Name"
url: "https://cafe.naver.com/cafename/123456"
source: naver-cafe
viewCount: 100
commentCount: 5
---
Article content...
Articles are saved to: {cafeFolder}/{cafeName}/{title}.md
Settings
Blog Settings
- AI Provider: OpenAI, Anthropic, Google, or Ollama
- Default Folder: Where blog posts are saved
- Image Folder: Where images are downloaded
- Enable AI Tags/Excerpt: Toggle AI features
- Enable Image Download: Download images locally
- Duplicate Check: Skip existing posts
Cafe Settings
- NID_AUT / NID_SES: Cookie values for private cafe access
- Cafe Import Folder: Where cafe articles are saved
- Download Cafe Images: Download images from cafe articles
- Exclude Notice: Skip notice/announcement posts
- Minimum Content Length: Filter short posts
- Duplicate Check: Skip existing articles
Supported Content
- Text, headings, quotes, code blocks
- Images with captions
- Ordered/unordered lists
- Horizontal lines
- YouTube embeds (native Obsidian format)
- Link cards / OG previews
- Videos (as links)
- Tables (basic support)
Development
git clone https://github.com/hyungyunlim/obsidian-naver-blog-importer.git
npm install
npm run build
Credits
Inspired by betarixm/naver-blog.md and Jeongseup/naver-blog-backer.
License
MIT License
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.