Softwr

Web Development · head to head

Drupal vs Preact

Drupal logo

Drupal

Web Development

Open-source CMS for complex, structured content sites

From
Free
Rated
-
Preact logo

Preact

Web Development

3kB alternative to React with the same modern API

From
Free
Rated
-

The short version

  • Each has a real cost: Drupal steep learning curve: concepts that are implicit in WordPress are explicit and must be configured; Preact compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
  • They diverge on capability: Drupal covers Structured content modelling, Preact covers 3kB runtime.

Where they differ

Only the attributes on which Drupal and Preact actually diverge.

Attributes where Drupal and Preact differ
AttributeDrupalPreact
PlatformsWeb, Linux, Self-hostedWeb

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), user rating (Not yet rated), category (Web Development).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Drupal

  • Structured content modelling
  • Granular permissions
  • Multilingual
  • Views

Only in Preact

  • 3kB runtime
  • preact/compat
  • Same modern API
  • Fast rendering

What people use each for

The jobs each tool is most often brought in to do.

Drupal

  • Government and university sites with complex content models and strict permissionsnot Preact
  • Multilingual sites where translation is structural rather than a pluginnot Preact
  • Publishers needing custom content types and editorial workflownot Preact

Preact

  • Embedded widgets that load inside someone else’s page and must stay smallnot Drupal
  • Marketing and content sites where JavaScript payload affects Core Web Vitalsnot Drupal
  • Applications targeting low-bandwidth or low-powered devicesnot Drupal

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Drupal

  • Steep learning curve: concepts that are implicit in WordPress are explicit and must be configured
  • Smaller developer pool than WordPress, and correspondingly higher build costs
  • Major version upgrades have historically been substantial projects, not routine updates
  • Considerably more machinery than a straightforward marketing site needs

Preact

  • Compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
  • Behavioural differences from React exist in edge cases, particularly around event handling
  • A much smaller community, so unusual problems have fewer existing answers than React

Pricing, plan by plan

Drupal

Free
  • DrupalFree
    • Full functionality
    • Commercial use permitted
    • Community support

Preact

Free
  • PreactFree
    • Full library
    • Commercial use permitted
    • No usage limits

Which should you pick?

Choose Drupal if

  • You need structured content modelling.
  • You want to start without paying.
  • You work on Web, Linux, Self-hosted.
  • You also want granular permissions.

Choose Preact if

  • You need 3kb runtime.
  • You want to start without paying.
  • You also want preact/compat.

Questions people ask

Is Drupal or Preact better?
Neither clearly leads. Drupal starts at Free and Preact at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Drupal or Preact?
Drupal starts at Free and Preact at Free.
Does Drupal or Preact run on more platforms?
Drupal runs on Web, Linux, Self-hosted. Preact runs on Web.
Can I use Drupal for free?
Both have a free tier, so you can try either at no cost before committing.
What is Drupal best used for?
Drupal is most often used for government and university sites with complex content models and strict permissions, multilingual sites where translation is structural rather than a plugin, publishers needing custom content types and editorial workflow. Of those, government and university sites with complex content models and strict permissions and multilingual sites where translation is structural rather than a plugin are not what Preact is typically brought in for.
What can Drupal do that Preact cannot?
Drupal covers Structured content modelling, Granular permissions, Multilingual, Views. Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering.

Answered from the vendors’ own pages

Drupal: Is Drupal free?

Yes, open source under the GPL. Costs are hosting, development and any commercial modules.

Preact: Is Preact free?

Yes, open source under the MIT licence.

Drupal: Drupal or WordPress?

WordPress is faster to launch, cheaper to staff and has a much larger plugin ecosystem. Drupal is stronger when the content model is genuinely complex and permissions are strict, which is why institutions favour it.

Preact: Can I use React libraries with Preact?

Most, through the preact/compat layer. Compatibility is good but not complete, so libraries relying on React internals can break.

Drupal: Why is Drupal common in government and universities?

Structured content modelling, granular access control and multilingual support are core rather than bolted on, and those are exactly the requirements those sectors have.

Preact: Why choose Preact over React?

Bundle size, almost always. If payload is not a binding constraint, React’s ecosystem is usually the better trade.

Share

Related pages

Other head to heads