/handbook/developing-for-block-editor-and-site-editor/custom-block-controls/
What We Do
Digital Platform MigrationsKey SolutionsManaged ServicesStaffing SolutionsIndustriesProducts
OnePress
Unify multiple brands on one governed WordPress platform.
Design & UI/UX
Gutenberg-native UX, UI, and design systems for visitors and editors.
WordPress Modernization
Modernize WordPress for better performance, architecture, and AI readiness.
WordPress as a DXP
WordPress as a composable DXP when monolithic systems no longer cut it.
Headless WordPress
Omnichannel content delivery without sacrificing marketing autonomy.
Frappe/ERPNext
Build scalable ERP and custom applications, from implementation to ongoing support.
Discovery
Strategic consultancy & project roadmap
Growth Services
On demand development & consultation
Site Maintenance
Annual maintenance. Done for you
QE Services
Testing across SDLC for assured quality
Hosting Migration
Move to a performant hosting with zero downtime
WooCommerce
Enterprise commerce delivered without lock-in
AI
Unlock real use cases and integrations
All Services
A suite of services for any need
Technology STACK
eCommerce
Scale your e-commerce with WooCommerce, integrations, and custom extensions for growth.
EasyEngine
Server management tool that makes using WordPress on Nginx easy.
Web Auditor
Performance Audit & Insights for your Website.
rtMedia
A complete media management plugin for WordPress.
Resources
About Us
CLEAR
Resources Developing for Block Editor and Site Editor Extending the editor Creating custom block controls
Topics
On this page
Understanding Sidebar (InspectorControls) vs Inline (Block-Level Controls)
InspectorControls (Sidebar Controls)
Inline (Block-Level Controls)
Dynamic Block Controls: Conditional Controls
Saving, Validating, and Rendering Block Controls
Saving Block Controls
Validating User Input in Block Controls
Optimizing Performance for Block Controls
Reducing Unnecessary Re-Renders
Styling and Accessibility in Block Controls
Using WordPress’s Built-in Component Library
Accessibility Considerations
Last updated on Mar 31, 2026
Developing Custom Block Controls
Block controls allow users to customize the appearance, layout, and behavior of blocks in the WordPress Block Editor. These controls provide an interface for users to make adjustments without needing to code, offering flexibility for users while keeping the editing experience simple.
Custom controls for core/cover block to pause/play video
For developers, understanding how to create these controls enables you to build powerful, user-friendly blocks that offer customization options directly in the editor.
Understanding Sidebar (InspectorControls) vs Inline (Block-Level Controls)
In the WordPress Block Editor, controls can be added either in the sidebar or directly within the block itself. Both types of controls serve different purposes and enhance the editing experience in their ways.
InspectorControls (Sidebar Controls)
InspectorControls appear in the right-hand sidebar when editing a block. These controls are used for settings that affect a block’s layout, style, or behavior without directly changing the block’s content. The sidebar is the best place for inputs like color pickers, text inputs, and toggles.
Example: Adding a TextControl and ColorPicker
import { __ } from "@wordpress/i18n";
import { useBlockProps, InspectorControls } from "@wordpress/block-editor";
import { PanelBody, TextControl, ColorPicker } from "@wordpress/components";
const Edit = (props) => {
const { attributes, setAttributes } = props;
const { text, backgroundColor } = attributes;
return (
<div {...useBlockProps()} style={{ backgroundColor }}>
<InspectorControls>
<PanelBody title={__("Block Settings")}>
<TextControl
label={__("Heading Text")}
value={text}
onChange={(newText) => setAttributes({ text: newText })}
/>
<ColorPicker
label={__("Background Color")}
color={backgroundColor}
onChange={(colorValue) =>
setAttributes({ backgroundColor: colorValue })
}
/>
</PanelBody>
</InspectorControls>
<h2>{text}</h2>
</div>
);
};
export default Edit;
- InspectorControls adds block settings to the sidebar, offering customization options without cluttering the main content area.
- TextControl provides a field for users to input the heading text.
- ColorPicker allows users to select a background color.
Inline (Block-Level Controls)
Also known as the block toolbar, these controls appear directly within or above the block when it is selected. They are designed to give users quick access to essential settings, such as text formatting, alignment, or other immediate adjustments. The block toolbar is all about making fast, in-context changes without navigating away from the block you’re working on.
Check out our detailed guide on creating and customizing block toolbars.
Dynamic Block Controls: Conditional Controls
Dynamic block controls change based on user input, making blocks more interactive and intuitive. For example, you might show a RangeControl for adjusting font size only if the user has enabled the option for custom font sizes.
Example: Conditionally Showing a Font Size Slider
import { ToggleControl, RangeControl } from "@wordpress/components";
const Edit = (props) => {
const { attributes, setAttributes } = props;
const { enableCustomFontSize, fontSize } = attributes;
return (
<div>
<ToggleControl
label="Enable Custom Font Size"
checked={enableCustomFontSize}
onChange={(value) => setAttributes({ enableCustomFontSize: value })}
/>
{enableCustomFontSize && (
<RangeControl
label="Font Size"
value={fontSize}
onChange={(value) => setAttributes({ fontSize: value })}
min={12}
max={100}
/>
)}
</div>
);
};
- The ToggleControl allows users to enable or disable custom font size settings.
- The RangeControl slider appears only if the toggle is enabled, keeping the interface clean and context-aware.
Saving, Validating, and Rendering Block Controls
When users interact with block controls, their input is saved as block attributes. These attributes are then rendered on the front end to reflect the user’s choices.
Saving Block Controls
Example: Saving and Rendering Block Attributes
const Save = (props) => {
const { attributes } = props;
const { text, backgroundColor } = attributes;
return (
<div style={{ backgroundColor }}>
<h2>{text}</h2>
</div>
);
};
Save function: This example renders the text and background color chosen by the user. When the content is saved, these attributes ensure the user’s customization appears both in the editor and on the live page.
Validating User Input in Block Controls
Validation ensures that users provide correct and appropriate input in block controls. For instance, you might validate the length of a text field or check if a URL is properly formatted.
Example: Validating Text Input Length
const validateInput = ( value ) => {
if ( value.length < 5 ) {
setError( 'Input must be at least 5 characters.' );
}
};
This function ensures the user provides text input with at least 5 characters, helping avoid invalid or incomplete data.
Optimizing Performance for Block Controls
Reducing Unnecessary Re-Renders
When a block re-renders too often, especially with complex controls, it can degrade performance. To improve performance, ensure that block attributes are only updated when necessary, and avoid expensive state updates.
Example: Using useCallback and useMemo to Optimize Re-Renders
import { useMemo, useCallback } from "react";
import { RangeControl } from "@wordpress/components";
const Edit = (props) => {
const { attributes, setAttributes } = props;
const { fontSize } = attributes; // Using useMemo to optimize fontSize range initialization
const fontSizeRange = useMemo(() => {
return { min: 12, max: 100 };
}, []); // Using useCallback to prevent re-creation of the handleFontSizeChange function
const handleFontSizeChange = useCallback(
(value) => {
setAttributes({ fontSize: value });
},
[setAttributes]
);
return (
<div>
<RangeControl
label="Font Size"
value={fontSize}
onChange={handleFontSizeChange}
min={fontSizeRange.min}
max={fontSizeRange.max}
/>
</div>
);
};
useMemo: Precomputes the font size range and prevents recalculation on every render.useCallback: Ensures that the handleFontSizeChange function isn’t recreated unnecessarily, avoiding extra processing and improving performance.
Styling and Accessibility in Block Controls
Using WordPress’s Built-in Component Library
WordPress provides components like TextControl, Button, and ColorPicker to help you maintain a consistent design across blocks. This ensures your custom controls fit naturally into the editor.
.custom-block-control {
margin: 10px 0;
padding: 5px;
}
Accessibility Considerations
Make sure your controls are accessible by:
- Using descriptive labels and tooltips.
- Adding ARIA attributes for screen readers.
- Ensuring keyboard navigation works seamlessly.
Example: Accessible Toggle Button
<ToggleControl
label="Enable Feature"
aria-label="Enable or disable custom feature"
checked={ isEnabled }
onChange={ ( value ) => setEnabled( value ) }
/>
By leveraging the power of InspectorControls, dynamic features like conditional controls, validation, and performance optimizations, you can create custom block controls that enhance both the user experience and the flexibility of the WordPress Block Editor. Focusing on performance and accessibility ensures that your blocks not only function well but also offer a seamless experience for all users.
Implementing block variations
PREVIOUS
Credits
Shreya Agarwal
Author
Shreya Agarwal
Author
Shreya Agarwal is a Growth Engineer at rtCamp, she brings active, hands-on WordPress development credentials to everything she writes and reviews. A WordPress Core Contributor with merged pull requ…
Good Work. Good People.
Industry partnerships
Compliance certifications
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Company
Solutions
Subscribe to Campfire for fresh insights and stories from people behind rtCamp
Δ
Email(Required)
Submit
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Cookie Consent
We value your privacy
We use cookies to give you the best possible experience. By clicking “Accept,” you consent to our use of cookies to improve site functionality, analyze usage, and personalize content and communications. Your privacy matters to us, and we are committed to handling your data responsibly and transparently. Please check our Privacy Policy for more details.
Manage PreferencesDon’t AllowAllow All
Why do we use cookies?
×
By clicking "Accept" or "Decline All" at the bottom, you consent to the use of cookies and other tools as described in our Cookie Policy in accordance with your settings and accept our Terms of Service.
Toggle EssentialEssential
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
30 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
Toggle CloudFlareCloudFlare
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
Name
Description
Duration
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
Toggle CommentsComments
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Toggle GodamGodam
GoDAM" is primarily a specialized WordPress plugin and media management service designed to enhance video hosting, marketing, and asset management directly within the WordPress dashboard.
Service URL: godam.io (opens in a new window)
Name
Description
Duration
user_image
Temporarily stores the path to the user's avatar or profile picture for quick rendering in the website header.
session
user_id
Stores the numerical ID of the logged-in user to maintain session continuity and basic site operations.
session
full_name
Stores the logged-in user's display name to personalize the site interface without needing database queries.
session
system_user
First-party cookie used to store basic application state identifying the current system user role.
session
sid
A generic session ID cookie used to maintain user state and functionality as the visitor navigates through the site.
session
Toggle Google reCAPTCHAGoogle reCAPTCHA
Google reCAPTCHA helps protect websites from spam and abuse by verifying user interactions through challenges.
Name
Description
Duration
_GRECAPTCHA
Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis.
179 days
Toggle Google Tag ManagerGoogle Tag Manager
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
cookiePreferences
Registers cookie preferences of a user
2 years
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
Toggle StatisticsStatistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Toggle Factors AIFactors AI
Factors.ai is a B2B account intelligence and marketing analytics platform that helps Go-To-Market (GTM) teams identify anonymous website visitors, track buyer journeys, and measure the ROI of marketing campaigns.
Service URL: www.factors.ai (opens in a new window)
Name
Description
Duration
_fuid
It is sent to capture session details and track user behavior across your website to provide behavioral data and intent signals.
1 Year
Toggle Google AnalyticsGoogle Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
Name
Description
Duration
FPGSID
Stores a session or user identifier to track how visitors interact with a website. This helps Google Analytics measure website performance, user engagement, and usage patterns.
Session
FPLC
Used by Google Analytics to link visitor interactions and sessions across multiple related domains.
20 hours
FPID
A server-side Google Analytics cookie used as an alternative user identifier when third-party cookies are restricted.
2 years
_ga
ID used to identify users
2 years
_ga_
ID used to identify users
2 years
Toggle Jetpack StatsJetpack Stats
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.
Service URL: automattic.com (opens in a new window)
Name
Description
Duration
tk_aip
Stores a list of anonymous visitor IDs so they can be merged into one identity once a visitor is recognized.
Up to 5 years
tk_tc
Used once per page load to work out which cookie domain the Tracks library should use, then removed as soon as it's read back.
Session (deleted immediately after use)
tk_qs
Queues analytics events for Jetpack's Tracks library so none are lost if the page closes before they can be sent.
30 minutes
tk_ai
Stores a randomly-generated anonymous visitor ID so Jetpack's Tracks analytics library can link tracking events to the same visitor.
Session in wp-admin; up to 5 years on the frontend
Toggle Microsoft ClarityMicrosoft Clarity
Clarity is a web analytics service that tracks and reports website traffic.
Service URL: clarity.microsoft.com (opens in a new window)
Name
Description
Duration
CLID
Identifies the first-time Clarity saw this user on any site using Clarity.
12 months
ANONCHK
Indicates whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn't use ANID and so this is always set to 0.
Session
_clck
Persists the Clarity User ID and preferences, unique to that site is attributed to the same user ID.
12 months
_clsk
Connects multiple page views by a user into a single Clarity session recording.
12 months
Toggle Parse.lyParse.ly
Parse.ly is a content analytics platform that helps publishers optimize audience engagement and content performance.
Name
Description
Duration
_parsely_session
JSON document storing information identifying a browsing session according to Parsely’s proprietary definition
30 minutes
_parsely_visitor
JSON document uniquely identifying a browser and counting its sessions
13 months
cookies.js_dtest
This cookie determines whether the browser accepts cookies.
session
Toggle MarketingMarketing
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Toggle Bing / MicrosoftBing / Microsoft
Bing, powered by Microsoft, is a search engine providing web, image, video, and map search capabilities.
Name
Description
Duration
MR
Used to collect information for analytics purposes.
6 months
ANONCHK
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
10 minutes
SM
Used by Microsoft in synchronizing the MUID across multiple Microsoft domains to track users for advertising.
session
MUID
Identifies unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes.
1 year
Toggle DoubleClick/Google MarketingDoubleClick/Google Marketing
A comprehensive digital advertising platform for managing campaigns, optimizing performance, and analyzing audience data.
Name
Description
Duration
IDE
This cookie is used for targeting, analyzing and optimisation of ad campaigns in DoubleClick/Google Marketing Suite
2 years
ar_debug
Store and track conversions
Persistent
Toggle LinkedInLinkedIn
LinkedIn is a professional networking platform for job seekers, employers, and industry connections.
Name
Description
Duration
bscookie
Used by LinkedIn to track the use of embedded services.
1 year
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries
30 days
bcookie
Used by LinkedIn to track the use of embedded services.
1 year
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
90 days
lidc
Used by the social networking service, LinkedIn, for tracking the use of embedded services.
1 day
UserMatchHistory
Used by LinkedIn Ads to synchronize and match user IDs across different ad networks and data providers.
30 days
Toggle LinkedIn InsightLinkedIn Insight
LinkedIn Insight is a web analytics service that tracks and reports website traffic.
Service URL: www.linkedin.com (opens in a new window)
Name
Description
Duration
li_sugr
Used to make a probabilistic match of a user's identity.
90 days
lidc
Used for routing and session management.
24 hours
Toggle LiveIntentLiveIntent
LiveIntent provides a platform for email advertising and identity-driven marketing solutions.
Name
Description
Duration
_lc2_fpi_js
Companion cookie to _lc2_fpi used by JavaScript to facilitate cross-domain ad tracking and user identification.
1 year
_lc2_fpi
First-party tracking cookie usually associated with LiveRamp to identify users across devices for targeted advertising.
1 Year
_li_ss
Sets a unique ID for the visitor, that allows third party advertisers to target the visitor with relevant advertisement. This pairing service is provided by third party advertisement hubs, which facilitates real-time bidding for advertisers.
1 month
lidid
Collects data on visitors' behaviour and interaction - This is used to make advertisement on the website more relevant. The cookie also allows the website to detect any referrals from other websites.
2 years
Toggle Cookie PolicyCookie Policy
You can find more information in our Privacy Policy.
Allow AllDecline All
Accept