Schedule posts to dev.to with LazyRelay

LazyRelay schedules markdown articles to dev.to using your API key, then checks that the article is really published and reachable. LazyRelay's difference is Proof-of-Publish: after a post goes out, it checks dev.to again to confirm the post is really live.

What you can post to dev.to

Text: dev.to publishes no post length limit that LazyRelay could verify, so this page does not state one (not verified). LazyRelay itself refuses posts over 5000 characters. The text is written in markdown.
Text-only posts are accepted.
Images: JPEG, PNG, WEBP, GIF, up to 20 MB each. Images are shown by address: the first is the cover image and the rest appear inside the article. The size limit is LazyRelay's general figure, not a verified dev.to limit.
Video: not supported.
Several files in one post: up to 10 images (no video in a multi-image post).
Title: the first line of your post is the title, unless you set a title under Platform options. LazyRelay caps titles at 250 characters, and dev.to publishes no title limit.
Tags: up to 4.
Series and canonical link: you can set a series, and an original address (an https link) if the article appeared elsewhere first.
Draft: you can save the article as a draft instead of publishing it.

LazyRelay checks file size and format before a post is scheduled and tells you which limit was hit. For the full comparison of what each platform supports, see What Works on Which Platform.

How to connect dev.to

On dev.to open Settings, then Extensions, and find DEV Community API Keys.
Type LazyRelay as the description and click Generate API Key. Copy the key.
In LazyRelay, open the Social Platforms tab and click the dev.to tile.
Paste the API key and click Connect.

How Proof-of-Publish works on dev.to

dev.to drafts do not show up publicly, so LazyRelay first looks for the article in your own list of articles, which includes drafts, and falls back to the public article page if needed. For a published article it then requests the public address with no credentials, the way a reader would, and requires that to answer successfully. A draft is reported as saved as a draft and never as confirmed live.

Want the general idea? Read Does Your Post Actually Publish?

Limits and things to know

dev.to has no video upload through its API, so a video is refused.
dev.to has no scheduling field, so LazyRelay publishes the article itself at the scheduled time.
dev.to's rate limits are not documented, and LazyRelay does not add a cap of its own.
A post saved as a draft is not public, so it is never marked confirmed live and it is not counted in analytics.

Schedule to dev.to and know it actually went live.

See plans and get started free

Frequently asked questions

Does dev.to support scheduling?

dev.to has no scheduling field of its own, so LazyRelay holds the article and publishes it at the time you set.

Can LazyRelay set tags, a series and a canonical link?

Yes. You can set up to 4 tags, a series, and an original address that must be an https link.

Can I save a dev.to article as a draft?

Yes. A draft is saved on dev.to and reported as saved as a draft. It is never marked confirmed live.

How do I know my dev.to article is really live?

LazyRelay finds the article through your account, then requests its public address with no credentials and requires that page to answer successfully.

Figures on this page come from LazyRelay's platform rules, checked on 2026-09-30. Sources: developers.forem.com/api/v1. Anything marked not verified has no published source.

Schedule to other platforms: Facebook · Instagram · TikTok · Pinterest · YouTube · LinkedIn · Threads · Mastodon · Bluesky · Telegram · Discord · Tumblr · WordPress · Hashnode · Lemmy · Slack