How to Add Custom WordPress Quicktags in the Text Editor + Examples

Custom WordPress Quicktags

Adding custom WordPress Quicktags to the text editor can save you time when writing new posts. Quicktags make it easier to insert HTML elements, custom classes, and more to the HTML of your posts, which speeds up your entire publishing process.

Before I get into how to add custom Quicktags, let’s review what they are.

What are WordPress Quicktags?

WordPress Quicktags are the buttons you see at the top of the WordPress editor when you’re in Text mode. They help you add additional styling, HTML elements, custom classes, and more to the HTML code of your posts.

Default WordPress Quicktags in the editor
Notice the “Text” tab is selected in the top-right

They are very similar to the TinyMCE buttons you see when you are in Visual mode.

Default TinyMCE buttons in WordPress editor
Notice the “Visual” tab is selected in the top-right

The WordPress Quicktags API makes it easy for us to create our own custom Quicktags. First, I’ll explain the available options, and then I’ll walk you through several real-life examples.

WordPress Quicktag Options

The QTags.addButton function allows us to customize 8 different options:

id (required)
the HTML id for the button
display (required)
the actual text that is seen on the button in the text editor
arg1 (required)
an opening tag, like <span>
arg2 (optional)
a closing tag, like </span>
access_key (optional)
a keyboard shortcut key to access the button
title (optional)
appears on hover; leave blank for no title
priority (optional)
a number representing the desired position of the button in the toolbar; lower numbers come before higher numbers
instance (optional)
limit the button to a specific instance of Quicktags; in most cases, leave this blank to add to all instances.

The first 3 options are required, and everything else is optional.

  • If you are adding a self-closing HTML tag (ex: <hr />), then you would leave arg2 blank
  • access_key is completely up to you and how you’ll use your Quicktags
  • title is helpful if the display doesn’t make it obvious what the button does
  • priority is helpful to organize your Quicktags in an order that makes sense to you
  • instance will most likely be left off because you’ll want the buttons to appear everywhere a Text editor is available

Now let’s get into the code and walk through some examples of how to use custom WordPress Quicktags.

WordPress Quicktags Examples

For seasoned WordPress veterans, it’s rather easy to identify many uses for Quicktags. They can be a huge time-saver. But for everyday WordPress users, the possibilities might not be as obvious.

The Quicktags you decide to add will ultimately depend on several factors:

  • The type of content you produce
  • The type of theme you’re using (purchased vs. custom)
  • Your level of knowledge with HTML & CSS
  • If you’re using a CSS framework
  • The type of editors you employ (writers vs. developers vs. content managers)

Let’s take a look at various ways to use WordPress Quicktags to give you some ideas what might be helpful in your specific situation.

Setting up the code

Before I get into each example, it’s important to know how to set up your code.

I highly recommend creating a custom plugin to store your code. This way, should you change themes in the future, your Quicktags will still be available. If not a custom plugin, I recommend the Code Snippets plugin by Shea Bunge. It allows you to add PHP code snippets to your site without the need for custom plugins or edits to your theme’s functions.php file.

Now that you’ve selected your method of implementation, let’s take a look at the base code. This will appear before and after all the examples I’m about to show you.


// Add Custom Quicktags to Text Editor
function smackdown_add_quicktags() {

	if ( wp_script_is( 'quicktags' ) ) { ?>
		<script type="text/javascript">
			...your custom Quicktags will go here...
	<?php }

add_action( 'admin_print_footer_scripts', 'smackdown_add_quicktags' );

The if ( wp_script_is( 'quicktags' ) ) piece just checks to make sure the Quicktags JavaScript is being loaded. This helps prevents potential errors or conflicts with other themes/plugins.

The middle section is the actual JavaScript that will create your custom Quicktags.

The last line is what prints that JavaScript out at the bottom of your WordPress admin pages, including the Edit Post and Edit Page screens, which is where your Quicktags will be used.

Here’s a full example if I wanted to add an <h2> Quicktag:


// Add Custom Quicktags to Text Editor
function smackdown_add_quicktags() {

	if ( wp_script_is( 'quicktags' ) ) { ?>
		<script type="text/javascript">
			QTags.addButton( 'h2_tag', 'h2', '<h2>', '</h2>', '', '', 1 );
	<?php }

add_action( 'admin_print_footer_scripts', 'smackdown_add_quicktags' );

To add additional WordPress Quicktags, just start each one on a new line. They all start with QTags.addButton, and must be present in-between the opening <script> and closing </script> tags.

Now let’s dive into some examples.

I’ve chosen to leave the access_key blank for all examples. The final number (1, in most examples) can be adjusted to move the Quicktag earlier or later in your toolbar.

WordPress Quicktags for Commonly Used HTML Elements

WordPress includes a handful of commonly used HTML elements in their default Quicktags. But you might have others that you use frequently. Here are a few I’ve found helpful.

Heading Tags <h2>, <h3>, etc.

The WordPress visual editor provides an easy way to add heading tags to your content. When in Visual mode, you can also use keyboard shortcuts for <h2>, <h3>, <h4>, etc. But when in Text mode, it’s not quite as easy. Enter Quicktags.

Use the code below to add WordPress Quicktags for common heading tags:

QTags.addButton( 'h2_tag', 'h2', '<h2>', '</h2>', '', '', 1 );
QTags.addButton( 'h3_tag', 'h3', '<h3>', '</h3>', '', '', 2 );
QTags.addButton( 'h4_tag', 'h4', '<h4>', '</h4>', '', '', 3 );

<small> tag

I make frequent use of the <small> tag, so this one saves me a lot of time.

QTags.addButton( 'small_tag', 'small', '<small>', '</small>', '', '', 1 );

<pre> code blocks

For developers, or anyone providing code in their tutorials, this one is essential. We need a quick way to add a <pre> tag around code examples. It’s also important to use proper semantics, which means following this format:

<pre><code> …code here… </code></pre>

I use the syntax highlighter prismjs, so I’ve taken this WordPress Quicktag one step further. I’ve added a language class to the <code> element, which tells prismjs how to highlight the code. I just replace the “none” with “php” or “javascript” or “html,” depending on what type of code it is. And then prismjs beautifully color codes it.

QTags.addButton( 'pre_code_language', 'pre', '<pre><code class="language-none">', '</code></pre>', '', 'Code Block', 1 );

BONUS: Checkout this great plugin that will add a TinyMCE <code> button to the Visual editor. A must-have for developers.

Definition Lists

The definition list is one of the most underutilized HTML elements out there. Maybe including it on this list will be a reminder for more to use it, when appropriate.

I’ve found it easiest to include the entire skeleton for a <dl> in arg1 (the opening tag), and just leave arg2 blank. Then I’ll simply copy/paste the blank <dt></dt> and <dd></dd> tags as many times as I need them, and then insert my terms & definitions.

QTags.addButton( 'dl_list', 'dl', '<dl>\n\t<dt></dt>\n\t<dd></dd>\n</dl>', '', '', 'Definition List', 1 );

The \n creates a new line and the \t creates a tabbed indent.

WordPress Quicktags for Buttons

If you’ve developed your own theme, you likely have a class that you add to <a> elements to style them like buttons. If you’re inserting these into posts or pages, it’s helpful to be able to quickly add your button class. This speeds up your writing, but also means you don’t have to remember the exact class names. It’s stored in your Quicktag for you.

QTags.addButton( 'btn_main', 'btn', '<a class="btn" href="#">', '</a>', '', 'Link button', 1 );

WordPress Quicktags for Responsive Video Embeds

If you embed videos on your site frequently, you probably add some code to make them responsive. I prefer the code found on, which is now also used by YouTube. But instead of applying the same inline CSS styles for every single video, I’ve created a global class, and added the CSS to my theme’s stylesheet.

I use <div class="embed-container"></div> around any <iframe> or other type of media that I embed.

After pasting the <iframe> code into my Text editor, I use this Quicktag to make it responsive:

QTags.addButton( 'embed_div', 'embed div', '<div class="embed-container">', '</div>', '', '', 1 );

SEE ALSO: How to embed YouTube videos in WordPress

WordPress Quicktags for Commonly Used CSS Classes

You might just have a need for adding custom classes to <div> or <p> tags that apply styling which you’ve set in your theme’s stylesheet. Here are a few that I use pretty regularly:

Messages, Alerts or Callouts

I use callout boxes to highlight notes, caveats, warnings, or just anything that I feel should stand out from the regular text of an article.

QTags.addButton( 'message_p', 'message', '<p class="message">', '</p>', '', '', 1 );


To prevent orphans and awkward line breaks, I’ll sometimes use the CSS property/value white-space: nowrap;. I apply it to anything with a class of nowrap.

QTags.addButton( 'nowrap_span', 'nowrap', '<span class="nowrap">', '</span>', '', '', 1 );

WordPress Quicktags for Popular Frameworks

While I don’t personally use a front-end framework for custom WordPress themes that I build, I know many people do. It can save you some time to have a few Quicktags to insert <div> tags with appropriate class names for the front-end framework of your choice.

Quicktags for Bootstrap

If you want to add 3 equal-sized columns in a row, you could use something like this:

QTags.addButton( 'bootstrap_grid', 'bootstrap grid', '<div class="container">\n\t<div class="row">\n\t\t<div class="col"></div>\n\t\t<div class="col"></div>\n\t\t<div class="col"></div>\n\t</div>\n</div>', '', '', '', 1 );

If you use Bootstrap alerts often, you could add a Quicktag for them as well. Just add the appropriate ending to the alert- class for success, info, warning or danger.

QTags.addButton( 'bootstrap_alert', 'bootstrap alert', '<div class="alert alert-" role="alert">', '</div>', '', '', 1 );

Quicktags for Foundation

In you prefer Zurb’s Foundation over Bootstrap, you can create Quicktags the same way.

Here’s an example for a Foundation callout:

QTags.addButton( 'foundation_callout', 'callout', '<div class="callout large">', '</div>', '', '', 1 );

Or a Foundation hollow button:

QTags.addButton( 'foundation_button_hollow', 'hollow button', '<a class="hollow button" href="#">', '</a>', '', '', 1 );

If you’re curious, here is a list of all the Quicktags I’m currently using on this site:

WordPress Quicktags in use on this site

If you create any awesome WordPress Quicktags, or have an idea for one, please share in the comments. I’ll add them to the list.

4 Commentson "How to Add Custom WordPress Quicktags in the Text Editor + Examples"

  1. /

    So i have a quick question, I’m using wordpress and using a pagebuilder to build pages. An element (.ac-text) is setting itself as H3 but I would like to have it as an H1, how do I go about this please?

    Would really appreciate.

    → Reply
    1. (Author) /

      Temak — Which page builder are you using? And what is the name of the element that you’re adding? Is it a “Text” element? A “Heading” element?

      If you could provide a screenshot, that would be even more helpful. I’ll try to help you out if you can provide this info.


    2. /

      Hi Dave – Thanks for your response. The page builder is CS Page Builder, I think its a custom one made for the theme based off Page Builder plugin. It is a Heading element currently showing as an H3 but I would like it as H1 instead.

      I can do this easily with the front editor when inspecting elements but would like to know how to do this from the backend so it takes effect.

      A screenshot is shown here:

      Thank you.

    3. (Author) /

      Hey Temak — I just replied privately to your email.

What Are Your Thoughts?

All fields are required. Your email will not be published.

You can use standard <code> and <pre> tags to post code examples, or a service like