Dev.to Guide: Stats & Devrel Playbook (2026)

Dev.to, styled DEV and run on the open-source Forem platform, is the largest general-purpose community feed built specifically for developers to publish long-form and short-form writing. Over 3 million registered developers, a homepage counter approaching 4 million accounts, and an acquisition by Major League Hacking in February 2026 make it one of the more consequential ownership changes in developer media this year.¹ This guide treats Dev.to as a distribution and devrel channel: what the platform actually is, how its feeds and tags decide who sees your writing, what canonical_url does for your SEO when you cross-post, and where it fits next to Hashnode, Medium, and your own company blog.

This is a long read (about 15 minutes). Use the table of contents to jump to what you need.

What is Dev.to?

Dev.to is a community publishing platform for software developers: a place to write tutorials, opinion pieces, build logs, and launch announcements, and to have them discovered by other developers through tag-based feeds rather than a personal follower graph alone. It is built on Forem, an open-source community platform that DEV's own team created and released, and the site itself runs as the flagship instance of that codebase.

Unlike GitHub, which centers on code and repositories (see our GitHub guide for that side of developer audience-building), Dev.to centers on prose: markdown articles, comment threads, reactions, and a reading list. Unlike a personal blog, articles on Dev.to inherit distribution from the platform itself: tag feeds, a Latest feed, a Top feed, and a weekly digest email that surfaces standout posts to the whole community.

Key Dev.to statistics in 2026

A note on the two membership figures. The homepage counter (approaching 4 million) counts every account ever registered, while MLH's own announcement cites 3 million registered software developers specifically. Both numbers come from Dev.to or its new owner, so we present them side by side rather than picking one as the "real" figure: over 3 million registered developers, with the homepage counter approaching 4 million accounts.

The Similarweb figures are third-party estimates, not numbers Dev.to itself has published, so treat the ~7.1 million monthly visits as a rough order of magnitude rather than an exact count. The consistent signal across both eras (2019's PR Newswire release and 2026's Similarweb estimate) is that organic search has always been the platform's single largest traffic channel, which matters directly for the canonical_url discussion below.

History and ownership: from a Twitter account to an MLH acquisition

Dev.to's origin traces back to 2014, when Ben Halpern started @ThePracticalDev, a Twitter account for developer humor and links. That account became the seed for dev.to, which launched properly in 2016 with Halpern, Jess Lee, and Peter Kim Frank as co-founders.²

The platform grew quickly on the strength of its community norms and searchability. In November 2019, the company raised an $11.5 million Series A led by Mayfield, at a time when it reported 5.5 million unique monthly visitors and 250,000 members.³ Jess Lee captured the growth-through-community framing at the time: "The growth of DEV is only possible because there are so many wonderful developers here who share our belief that the software industry can be inclusive to everyone."⁴

In 2020, the team open-sourced the underlying platform as Forem, short for "For Empowering Community," and the parent company became Forem Inc.⁵ Any organization or community can self-host a Forem instance; dev.to itself remains the flagship, most-trafficked instance of that codebase.

The most recent chapter arrived on February 18, 2026, when Major League Hacking (MLH) acquired DEV, with financial terms undisclosed. Peter Frank was DEV's CEO at the time of the deal. MLH's announcement framed the combined organizations as reaching 5 million developers, roughly 10 percent of all software engineers globally, and named a roster of ecosystem partners including Google Gemini, GitHub, ElevenLabs, Snowflake, DigitalOcean, Meta, Microsoft, and AWS.⁶ MLH and DEV both committed to continuing Forem as an open-source project. MLH's CEO, Mike Swift, summarized the pairing this way: "MLH is where you build and break things in person. DEV is where those lessons live on."⁷ Peter Frank added: "Joining MLH lets DEV remain that everyday gathering space for developer knowledge while benefiting from MLH's deep roots."⁸

Ben Halpern's own long-term framing of the company, from an Indie Hackers AMA, is worth quoting because it explains why the platform survived long enough to reach this point: "I really committed to making it a 10 year commitment. I wouldn't give up for 10 years even if nobody was visiting it after year 3."⁹ He also described the tradeoffs of building a values-driven community platform bluntly: "You have to be willing to frustrate some people in order to stick to your personal values along the way."¹⁰

How distribution works: feeds, tags, and Top 7 badges

Dev.to's discovery layer has three named feeds:

• Relevant: a personalized feed, the default view for logged-in users
• Latest: strictly chronological, newest posts first
• Top: ranked by engagement over a selectable period (day, week, month, year, infinity)¹¹

The Relevant feed is the one most writers care about and the one that is hardest to game. Community members who have examined the open-source Forem scoring code (a reverse-engineering exercise, and one that may not reflect the current production algorithm) describe a blend of factors: weight for tags the reader already follows, a boost from reactions the post has accumulated, a bonus if the reader already follows the author, a language-match signal, and some random jitter to keep the feed from feeling static.¹² Because this is community analysis of open-source code rather than an official DEV specification, treat it as a reasonable mental model, not a guaranteed formula.

Tags are the backbone of discovery. Each post carries up to four tags, and readers follow tags the way they'd follow a topic on other platforms. A post that lands cleanly in a reader's followed tags is far more likely to surface in their Relevant feed than one relying on Latest-feed luck. Dev.to also maintains a reading list (save for later) and roughly 30 recognition badges, covering things like the weekly Top 7 must-read list, the Fab 5, and posting-streak badges.¹³ The Top 7 in particular feeds into DEV's weekly digest newsletter, which is a meaningful secondary distribution channel beyond the on-site feeds.

SEO strength and canonical_url, explained properly

Dev.to's domain carries real search authority, and organic search is consistently its top traffic channel (an estimated ~48% of desktop visits per Similarweb).¹⁴ That authority is a double-edged sword for anyone who also runs their own blog: if you publish the same article natively on both your blog and dev.to with no coordination, Google may end up ranking the DEV copy above your own site for that content, simply because dev.to's domain out-competes a smaller personal or company blog.

The fix is the canonical_url field, set either in an article's front matter or through the editor's post options when importing or cross-posting. Setting canonical_url to your original blog post tells Google (and other search engines) which URL is the "real" one; search traffic and ranking credit flow to that URL, while the dev.to copy still participates fully in the tag feeds, reactions, and comment community.¹⁵ Josh Dzielak summarized the mechanism directly: "Google will send visitors directly to your site when the post appears in their search results and the post will accrue to your site's SEO."¹⁶ DEV's own RSS import tool can set the original source as canonical automatically when you connect a blog feed, which is the lowest-effort way to keep this consistent across every future post.

Content formats: markdown, series, liquid tags, and organizations

Writing on Dev.to happens in a markdown editor backed by Jekyll-style front matter. The fields that matter most:

---
title: Your Post Title
published: false
description: A one-line summary for previews and meta tags
tags: webdev, javascript, tutorial, career
canonical_url: https://yourblog.com/original-post
cover_image: https://yoursite.com/cover.jpg
series: My Tutorial Series
---

tags is capped at four. canonical_url is what protects your own site's SEO when cross-posting, as covered above. cover_image should be 1000 by 420 pixels, the platform's recommended dimension for the banner that appears at the top of the article and in feed previews.¹⁷ series groups related posts into a numbered sequence with automatic prev/next navigation, useful for multi-part tutorials.

Dev.to also supports liquid tags, a set of embed shortcodes that render rich content inline: {% embed URL %} is a universal embed that handles YouTube, X posts, GitHub gists and repos, CodePen, and Spotify without needing separate syntax for each. Additional tags include {% link %} (rich link previews), {% user %} (mention a profile card), {% tag %}, {% details %} (collapsible sections), and {% katex %} for math notation.¹⁸

Organizations are free company pages on Dev.to: branded posts, a per-post call-to-action, follower notifications when the org publishes, and basic analytics, all at no cost.¹⁹ For a devrel team, an organization page is the natural home for company-authored posts, distinct from individual engineers' personal profiles.

Finally, Listings function as a classifieds section: job postings, events, and mentorship offers, some of which are paid via platform credits rather than the free-by-default article publishing.

The API and devrel automation

Dev.to runs on the Forem API v1, documented at developers.forem.com/api/v1. Requests use an accept: application/vnd.forem.api-v1+json header and an api-key header, with keys generated under Settings > Extensions in your account.²⁰

Publishing an article is a single POST to https://dev.to/api/articles with an article object carrying title, body_markdown, published, tags, series, main_image, canonical_url, organization_id, and description. Updating an existing post is a PUT to /api/articles/{id}.²¹

For devrel teams running any kind of content pipeline, this API is what turns Dev.to from a manual chore into an automated syndication target: push a draft from CI when a company blog post publishes, set canonical_url programmatically so SEO stays with the source, publish under organization_id so it appears on the brand's org page rather than an individual's profile, or rely on RSS auto-import to pull posts in continuously.²²

Why developers and devrel teams publish there in 2026

The case for publishing on Dev.to comes down to distribution economics. A brand-new account with zero existing audience can still reach real readers immediately through the tag feeds, something that is not true of a standalone blog, which depends entirely on search indexing and external promotion to get its first readers. Because the domain carries genuine search authority, a well-tagged post can also rank in Google on its own merit.²³

The canonical_url mechanism removes the historical objection to syndication: it used to be genuinely risky to publish the same content in two places because of duplicate-content SEO penalties, and Dev.to's canonical support largely neutralizes that risk, letting a company blog remain the authoritative source while the DEV copy still earns community reach.²⁴ Organization pages give devrel teams a branded, analytics-backed presence for free, which is a meaningfully lower cost of entry than most alternatives.

The community's own norms play a role too. Dev.to's culture rewards tutorials, honest build-in-public logs, and launch posts, with a comment culture that stays notably beginner-friendly compared to some other developer forums. Practitioner consensus among devrel writers is to publish on your own blog first, then syndicate to Dev.to with a canonical link, rather than treating dev.to as the primary source.²⁵

The honest caveat: multiple angles of evidence point to rising volume alongside declining per-article engagement. One community analysis covering roughly a million articles published between December 2022 and January 2026 found that about 90 percent of articles are six-minute reads or shorter, consistent with a platform absorbing an enormous and growing volume of shorter posts.²⁶ That analysis is unofficial and community-produced, not a DEV-published statistic, but it lines up with the broader pattern devrel practitioners describe: as more content floods the tag feeds, any single article's expected reach and engagement trend downward even as the platform's total audience grows. The practical implication is that consistency and precise tag targeting now matter more than they did in Dev.to's earlier, less crowded years, and a single one-off post is a weaker bet than a sustained cadence.

Dev.to vs Hashnode vs Medium vs your own blog

Dev.to's advantage is scale of built-in discovery specifically for developers: no other platform on this list matches its tag-feed reach for a brand-new technical writer. Its tradeoff is that authority accrues to dev.to's domain unless you deliberately manage canonical_url.

Hashnode inverts that tradeoff: it lets you map a blog to your own custom domain so SEO value accrues to you from day one, with more control over theming and ownership, at the cost of a smaller discovery feed than Dev.to's. Note that several Hashnode features moved behind a paid Pro plan in 2026, which changes the free-tier comparison from a few years ago; see our Hashnode guide for the current details.

Medium has the largest audience in absolute terms but weak native support for code blocks and markdown, paywall friction that turns away some readers, and an audience mix that skews non-developer relative to Dev.to or Hashnode.

An owned blog (including a self-hosted WordPress site) gives full ownership and zero platform risk, but has no built-in distribution at all; every reader has to be earned through search, existing audience, or syndication elsewhere.

The 2026 devrel consensus across multiple practitioner write-ups is consistent: treat your own blog as the canonical source of record, and syndicate outward to dev.to (and optionally Hashnode) with canonical_url set on each, rather than picking a single platform to live on exclusively.²⁷

In practice, most teams settle on a simple decision tree. If the goal is maximum near-term reach on a launch day post, publish to Dev.to first and canonical it back to the company blog once the blog post is live, so the earliest readers land on dev.to's feed while search engines still credit the brand's own domain over time. If the goal is long-term compounding SEO value for a specific evergreen tutorial, publish on the owned blog (or a Hashnode blog mapped to a custom domain) first, and treat the Dev.to copy purely as a distribution mirror. Neither approach requires giving up the other platform; the only discipline required is remembering to set canonical_url every single time, since a single missed cross-post can quietly hand ranking credit to the wrong domain.

Posting in practice: scheduling and cross-posting with posterly

Dev.to has no native scheduling UI: articles publish immediately when you flip published to true, whether through the web editor or the API. The Forem API does support creating a post as an unpublished draft ahead of time, but turning that draft into a scheduled, timed publish still requires something outside dev.to itself.

That's the gap posterly closes for devrel workflows. posterly schedules Dev.to posts for a specific future publish time as part of the same calendar you use for your other 18 supported platforms, and it carries canonical_url support through so a cross-posted article keeps crediting your original source for SEO, exactly per the mechanism described above. For a devrel team publishing the same tutorial to a company blog, Dev.to, and other channels on a coordinated schedule, that means setting the canonical link once and letting the publish time, tags, and organization attachment stay consistent without a manual copy-paste step for every post. See the Dev.to scheduler page for the specifics, and our platform-specific content guide for how tutorial-style writing differs from what performs on non-developer platforms.

Final word

Dev.to in 2026 is bigger, more corporately backed (via the MLH acquisition), and more crowded than it was a few years ago. Over 3 million registered developers, a homepage counter nearing 4 million, and an estimated 7 million monthly visits make it one of the largest developer-specific audiences available to any writer or devrel team, at zero cost to publish. The tag feeds and Top 7 badges still reward focused, well-tagged writing, and canonical_url still means cross-posting costs you nothing in search rankings if you set it correctly.

The honest tradeoff to plan around is rising volume against declining per-article engagement: a single post is a weaker bet than it used to be, and consistency plus precise tagging now do more of the work. Pair that with a canonical strategy that keeps your own blog (or a platform like Hashnode where SEO accrues to your domain) as the source of record, and Dev.to remains one of the highest-leverage free distribution channels a developer-focused writer has.

For the broader landscape of where else technical content performs, see our platform guides and our pricing if you're ready to put scheduling and cross-posting on autopilot.