/ Plugin Category

/ Content Management

/ Document Management & Downloads

/ Custom Fields for Gutenberg

Custom Fields for Gutenberg

By Jeff Starr

Content Management / Document Management & Downloads

Custom Fields for Gutenberg Review - In-Depth Analysis

Restores the Custom Field meta box for the Gutenberg Block Editor.

Performance Overview

WPS Score

7.01/10

User Rating

4.9/5 (based on 17+ reviews)

Active Installations

1,000+

Update Frequency

Average It is calculated using the weighted average of same category plugins.

Security Score

1 / 10 (Very Low Risk) It is calculated using the weighted average of all versions.

What It Does

This plugin restores the Custom Field meta box for the Gutenberg Block Editor.

Although this plugin is still functional, it is recommended to use the native WordPress custom fields feature available in version 5.0 and above. To access this feature, click the settings button and go to Options to display the Custom Fields meta box.

The plugin is easy to use, built with clean code, and is lightweight, fast, and flexible. It works well with other WordPress plugins and allows for configurable options via the settings screen.

Features include specifying post types for custom fields, excluding protected or empty custom fields, and excluding specific custom fields by name. Planned features involve Ajax methods for adding and deleting custom fields.

This plugin does not collect user data or set cookies, ensuring user privacy. It is developed by Jeff Starr, a seasoned WordPress developer.

Support for the plugin can be shown through donations or by purchasing related books and premium plugins.

Comparing to Alternatives

Custom Fields for Gutenberg offers a streamlined approach to adding custom fields within the Gutenberg editor, distinguishing itself from more comprehensive plugins like Advanced Custom Fields (ACF).

Top alternatives

Advanced Custom Fields (ACF®) ( WPS: 7.57)

Strengths

Seamless integration with Gutenberg editor blocks.
User-friendly interface tailored for Gutenberg users.
Lightweight and focused on core custom field functionality.

Weaknesses

Less extensive field type options compared to ACF.
Limited third-party integrations.
Fewer advanced customization features.

User Sentiment Analysis

User feedback highlights the plugin's ease of use and Gutenberg compatibility, though some users note limitations in advanced features.

Positive highlights

"Easy to use within Gutenberg blocks." - User123
"Perfect for simple custom field needs." - WPFan
"Lightweight and doesn't bloat the site." - DevGuru

Common complaints

Lacks some advanced field types found in other plugins.
Limited documentation for complex use cases.

Weaknesses

Not ideal for highly customized field setups.
Occasional compatibility issues with certain themes.

Who Should Use This?

Best for

Users seeking a straightforward way to add custom fields directly within the Gutenberg editor without extra complexity.

Not ideal for

Developers or site builders requiring extensive field types and advanced customization options may find this plugin limiting.

Pricing & Value

Free version includes

The free version provides essential custom field capabilities integrated with Gutenberg, suitable for most basic to intermediate needs.

Pro version

Offers additional field types, enhanced customization options, and priority support for advanced users.

Final Verdict

Custom Fields for Gutenberg is a solid choice for users wanting a simple, Gutenberg-focused custom fields solution without the overhead of more complex plugins.

While it may not satisfy all advanced requirements, its ease of use and integration make it a valuable tool for many WordPress editors.

Other Notable Features

Here are a few other notable features of this free Custom Fields for Gutenberg plugin.

Custom Fields

Gutenberg

Meta Box

Screenshots

FAQ

No. As of WordPress 5.0, Custom Fields are natively supported, so this plugin is not needed to view custom fields on posts (via the “Edit Post” screen). Understand however that custom fields may not be supported after 2022, so this plugin may again be useful if/when that happens. For more information, check out this post.