Background
When copying local Markdown articles to other platforms, I found that the text could be transferred while the images still pointed to local files. To reduce the work of preparing each image individually, I created MDBlogPacker to include local images in the exported text.
Everyday writing can continue to use the original Markdown and separate images, with a copyable version generated when publishing across platforms.
Reproduction Environment
The inputs are local Markdown and image files. Image references may use standard Markdown syntax or Obsidian Wiki image references.
The target publishing platform needs to allow Base64 embedded images and accept the resulting article size. The tool offers both GUI and command-line interfaces.
Specific Problem
A local computer’s ability to resolve a relative path does not mean the target platform can access the same file. When only text is copied, image files do not move with it, potentially leaving blank images or broken references after publication.
Solution
Before selecting an export method, consider when to use separate images, remote URLs, or Base64 embedding. A site that can manage its own assets may need a different approach from an editor that only accepts pasted content. For guidance, read the image publishing approach details.
MDBlogPacker recognizes standard Markdown image syntax and Wiki image references, reads local images, and converts them into Base64 embedded format. Remote images and images already embedded remain unchanged.
The converted result can be copied or exported to a file for publication. The original article and images remain the sources to maintain, so later changes do not require direct editing of long encoded blocks.
Embedding increases text size, so the target platform’s acceptance rules and the final page appearance still need to be checked before publication.
Conversion through the GUI or CLI reduces the need to prepare each local image individually when transferring an article.
Successful display depends on the target platform’s support for embedded images. For websites that can manage their own assets, synchronizing images separately remains useful for caching and later replacement.