How ZyVOP handles cover images, relative asset resolution, and cross-platform image hosting.

Media & Asset Handling

Publishing to external targets requires that all image assets be publicly accessible over HTTPS so destination servers can download or hotlink them.

Relative Asset Resolution

If you store Markdown posts alongside local screenshots and diagrams in your Git repository:

my-blog/
├── posts/
│   ├── distributed-tracing.md
│   └── assets/
│       └── trace-waterfall.png

distributed-tracing.md

![Trace Waterfall Diagram](./assets/trace-waterfall.png)

External platforms (DEV.to, Hashnode, Medium) cannot access ./assets/trace-waterfall.png. ZyVOP solves this through Base URL Resolution:

Specify base_url in your frontmatter, pass --base-url via CLI, or let ZyVOP infer it from canonical_url.
The CLI or API converts all relative image references to absolute URLs:
- Input: ./assets/trace-waterfall.png
- Output: https://myblog.dev/posts/assets/trace-waterfall.png

Frontmatter Example

---
title: "Distributed Tracing"
canonical_url: "https://myblog.dev/posts/distributed-tracing"
base_url: "https://myblog.dev/posts"
---

Your cover image is used as the article header across platforms and populates social Open Graph previews.

cover_image: "https://myblog.dev/images/microservices-banner.png"

Dimensions: 1200 x 630 pixels (standard 16:9 ratio for Open Graph cards & LinkedIn).
Format: PNG, JPG, or WebP.
File Size: Keep under 5MB to ensure fast loading on mobile networks.
Hosting: Must be hosted on a public HTTPS server (e.g. GitHub raw, S3, Cloudinary, or your personal blog domain).

Platform	Image Size Limit	Supported Formats
DEV.to	Max 25MB per image	PNG, JPG, WebP, GIF
Hashnode	Max 20MB per image	PNG, JPG, WebP, GIF
Medium	Max 25MB per image	PNG, JPG, WebP, GIF
Bluesky	Max 1MB (link thumbnail)	PNG, JPG, WebP
WordPress	Configured by server (typically 2MB - 64MB)	All standard formats