This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.

Cloud Blocks


Gutenberg Cloud: Your online library of blocks! Cloud Blocks is the only plugin you need to browse and install new blocks:

  • Discover and install custom blocks with a click
  • Install only the blocks you need – no huge plugin collections needed
  • Reuse blocks between WordPress and Drupal
  • Serve the blocks from a CDN

Why use Gutenberg Cloud?

Installing an actual plugin for each block or block collection easily leads to managing lots of code that you don’t really need. It’s like having one app for each website you visit, instead of just installing a web browser. With the block manager, you have a growing library at your fingertips, without the bloat.

Getting started

  1. Install the plugin
  2. Click the new cloud icon in the main menu
  3. Browse around and click a block to see description, version and bigger screenshot
  4. Activate a few blocks. Voila – these are now available to you in the Gutenberg editor!

How it works under the hood

Gutenberg Cloud is a service that fetches Open Source Gutenberg blocks hosted on NPM. The assets from these are served from CloudFlare using The Cloud Blocks plugin provides an interface in WordPress for Gutenberg Cloud.

Code once, use everywhere: Since the blocks are JS/CSS only, they are CMS agnostic. This means you can develop a block for a Drupal site, and reuse it later on a WordPress blog.


  • Discover and install blocks


Install it just like any other plugin. It just works!


Is it secure to run blocks from other people?

All blocks go through a manual code review before they are published. Waiting for a code review? Email

How do I migrate a block collection plugin to Gutenberg Cloud?

This simply means removing some PHP, adding some meta data and publishing on NPM. Follow these simple steps.

How do I create a custom block for Gutenberg Cloud?

Gutenberg Cloud blocks are really just normal Gutenberg blocks, without the PHP. Follow these steps to do it!

How do I disable CSS for a single block?

This is useful for letting your theme control your block styles. There’s a hook for this, documented here.

Why is the plugin called Cloud Blocks?

We wanted to name it Gutenberg Cloud, but since it’s not possible to name a plugin starting with the name of another plugin (i.e. Gutenberg), we ended up calling it Cloud Blocks. Makes sense though, doesn’t it?

Are the blocks really served from “the cloud”?

Indeed, they are! The source code for each block is on NPM, but the JS/CSS is served by a CDN. No local downloads!

Can I add private custom blocks?

Sure! Just add your custom blocks into wp-content/uploads/gutenberg-blocks/ folder. This is what the folder structure should look like!


14 maja, 2019
This is a fantastic idea. The concept of an cloud-based plugin store, coupled with single-purpose blocks — I love it. Just for experimentation, I tested the StarterX block, and yes, it installed and works on-page. My only concern is whether the cloud repository can scale for millions of users.
3 aprila, 2019
This is super cool, but after you click install on one these blocks, it confirms you installed it…only to then not have done anything at all. It won’t appear as installed, and going to a page with Gutenberg, the ones you tried to install won’t show up. When you go back, it gives the option to install them again. Rinse and repeat and they’ll never be installed. I’m really excited about this, but I can’t seem to get it to work, and its currently too young to see anyone else with a similar problem on record. I’ll change my review if there’s any way to fix the problem.
21 januarja, 2019
This concept, having a common repo for blocks, accessible directly from WP admin, just like for plugins and themes, is the way to go. You can select exactly the blocks you neeed with a click and disable them also with a click. No need to have users see a lot of listed blocks that just happen to be installed by plugin that has only one block you really need. Nothing is downloaded, they work from the cloud. Can be network activated. But more, as you can add local blocks that become visible in special tab on the Cloud Blocks activation/deactivation screen. And you can contribute to the global repo through NPM.
9 novembra, 2018
The great thing about the Gutenberg editor are blocks, and the great thing about blocks is Gutenberg Cloud as their repository. This plug-in is the only one you’ll ever need to expand the selection of blocks for your website. From a user perspective, adding blocks works the same way like adding themes or plug-ins, so it’s simple, fast and intuitive. If you are using Gutenberg, you absolutely need this plug-in.
Read all 5 reviews

Contributors & Developers

“Cloud Blocks” is open source software. The following people have contributed to this plugin.


“Cloud Blocks” has been translated into 3 locales. Thank you to the translators for their contributions.

Translate “Cloud Blocks” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.



*Fix: Fix an issue with local blocks directory which was losting every files as block


  • Fix: Fix db error in activator hook
  • Change: Dlete db table on plugin uninstallation


  • Fix: Fix missing slash in local blocks


  • Change: Replace CDN in favor of


  • Change: Update counter as a WP CRON (Thanks to ajotka)
  • Change: Update some docs
  • Fix: Fix polish translations


  • Fix: Fix some translations
  • Fix: Fix database table issue if plugin network activated issue #13
  • Cleanup: Remove custom_blocks method since its not used anymore. This method was for scanning local blocks inside /wp-content/gutenberg-blocks directory


  • Fix: Fix wrong label in block details issue #9
  • Fix: Fix network activation issue issue #11
  • Add: Polish translation. (Thanks to ajotka)
  • Add: Update counter & label in menu. (Thanks to ajotka)


  • Fix: Update blocks if new version available on the cloud
  • Enhancement: Improvement in local block screenshots. The filename can be both screenshot or thumbnail and it could be in blocks root directory or build folder


  • Fix: Change array dereferencing in activation hook
  • Fix: Show block in installed list even after block removed from Gutenberg Cloud
  • Fix: Don’t display Installed notice on blocks in Installed tab
  • Fix: Search blocks in installed and local blocks
  • Add: Listing for local custom blocks, install and delete them (In previous versions, blocks were activated automatically, from now on, you need to explicitly activate/deactivate them in the “Local” tab.)
  • Add: Default block screenshot
  • Change: Change minimum required php version
  • Change: Check for db structure update in upgrader_process_complete hook instead of init


  • Fix: Fix block js dependency introduced in Gutenberg 4.5.1


  • Change: Change increase and decrease number of installations of a block


  • Fix: Fix some issues in previous version release


  • Change: Private custom blocks now should be under wp-content/uploads/gutenberg-blocks/
  • Add: Implement UI to upload zip file with custom block issue #3
  • Fix: Fix a bug about enqueue custom blocks assets issue #4
  • Fix: Fix an issue with javascript if search query is empty


  • Add: Implement order for blocks (Latest or Popular)
  • Fix: Block counter in popular and latest tabls
  • Fix: Display block author
  • Change: Blocks homepage url
  • Change: If there is no installed blocks, redirect to Popular tab instead of Installed
  • Change: Update documentations


  • Add: Add modal with block info (like themes) issue #2
  • Fix: Limit enqueue of block styles only to editor or front-end


  • Fix: Fix translations variable name in javascript files
  • Change: Update readme


  • Change: Update readme
  • Add: More docs


  • Change: Some translation fixes
  • Change: Better documentation and screenshot
  • Added: Italian translation. (Thanks to cipo28)


  • Fix: is_plugin_active() undefined fix
  • Fix: Change strings functions to static


  • Initial plugin