What Is the Hello Dolly WordPress Plugin? Should You Delete It?

If you’ve ever installed WordPress, you might have noticed a curious plugin lingering in your dashboard: Hello Dolly. It doesn’t add contact forms, optimize images, or improve SEO. Instead, it displays a random lyric from Louis Armstrong’s 1964 hit “Hello, Dolly!” in your admin dashboard. For many users—especially beginners—this plugin raises a simple question: What is Hello Dolly, and why is it here? More importantly: Should I delete it?

In this in-depth guide, we’ll explore Hello Dolly’s origins, how it works, its purpose (or lack thereof), and whether it deserves a place on your WordPress site. By the end, you’ll have a clear understanding of this quirky plugin and be able to decide if it’s worth keeping.

Table of Contents#

  1. What Is the Hello Dolly WordPress Plugin?
  2. History and Origins: Why Was Hello Dolly Created?
  3. How Hello Dolly Works: A Technical Breakdown
  4. The Purpose (and Lack Thereof) of Hello Dolly
  5. Pros and Cons of Keeping Hello Dolly
  6. Security Considerations: Is Hello Dolly a Risk?
  7. Performance Impact: Does It Slow Down Your Site?
  8. Should You Delete Hello Dolly? A Decision Guide
  9. How to Delete Hello Dolly (Step-by-Step)
  10. Alternatives to Hello Dolly
  11. Conclusion
  12. References

What Is the Hello Dolly WordPress Plugin?#

Hello Dolly is a default, lightweight WordPress plugin that adds a small widget to your admin dashboard displaying a random lyric from “Hello, Dolly!” by Louis Armstrong. It has no settings, no configuration options, and no practical functionality for website visitors or even most site owners.

At its core, Hello Dolly is a minimalist plugin. It doesn’t interact with your site’s front end, database, or user data. Its sole job is to inject a bit of musical nostalgia into your WordPress admin experience.

If you’ve never noticed it, check your dashboard: It typically appears as a small box titled “Hello Dolly” in the right-hand column, alongside other widgets like “At a Glance” or “Activity.”

History and Origins: Why Was Hello Dolly Created?#

To understand Hello Dolly, we need to travel back to 2005. That year, WordPress released version 1.5, codenamed “Strayhorn” (after jazz composer Billy Strayhorn). Alongside this update, co-founder Matt Mullenweg introduced Hello Dolly as a default plugin.

But why “Hello, Dolly!”? Mullenweg has cited the song’s cultural significance and his personal fondness for it. In a 2014 interview, he explained that the plugin was intended as a lighthearted Easter egg and an educational tool for new developers.

At the time, WordPress was still a fledgling platform, and many users were new to plugin development. Hello Dolly’s simplicity—just 15 lines of functional code—made it the perfect example of how to build a basic plugin. It demonstrated core WordPress concepts like:

  • Using hooks (e.g., wp_dashboard_setup to add a widget).
  • Creating dashboard widgets.
  • Basic PHP logic (randomly selecting lyrics from an array).

In short, Hello Dolly was never meant to be useful. It was a teaching tool wrapped in nostalgia—a way to welcome new developers to WordPress with a familiar, friendly example.

How Hello Dolly Works: A Technical Breakdown#

Let’s dive into the code to see how Hello Dolly operates. The plugin consists of a single file: hello.php, located in /wp-content/plugins/hello-dolly/ (if installed).

Core Functionality#

The plugin’s code is refreshingly simple. Here’s a simplified breakdown of its key components:

  1. Plugin Header: A comment block at the top defines the plugin’s name, author, version, and description (required for WordPress to recognize it as a plugin).

    /*  
Plugin Name: Hello Dolly  
Plugin URI: https://wordpress.org/plugins/hello-dolly/  
Description: This is not just a plugin, it symbolizes the hope and enthusiasm of an entire generation summed up in two words sung most famously by Louis Armstrong: Hello, Dolly. When activated you will randomly see a lyric from <cite>Hello, Dolly</cite> in the upper right of your admin screen on every page.  
Author: Matt Mullenweg  
Version: 1.7.2  
Author URI: https://ma.tt/  
*/

  2. Lyric Array: A PHP array containing 16 lyrics from “Hello, Dolly!” (e.g., “Hello, Dolly, well, hello, Dolly” or “It’s so nice to have you back where you belong”).

  3. Dashboard Widget Function: A function (hello_dolly_widget()) that selects a random lyric from the array and displays it in a dashboard widget.

  4. Widget Registration: A function (hello_dolly_setup()) that hooks into wp_dashboard_setup to add the widget to the dashboard.

  5. Hooking It All Together: The hello_dolly_setup() function is registered to run when WordPress initializes, ensuring the widget appears on every dashboard load.

Key Takeaway#

Hello Dolly does nothing else. It doesn’t load stylesheets, JavaScript, or database queries. It doesn’t collect data or interact with other plugins. It simply runs a tiny bit of PHP to display a lyric in your admin area.

The Purpose (and Lack Thereof) of Hello Dolly#

Educational Value#

As mentioned, Hello Dolly’s original purpose was educational. For new developers, it served as a “Hello World” example for WordPress plugins. Its code is so simple that even beginners could study it to learn:

  • How to structure a plugin file.
  • How to use WordPress hooks to extend functionality.
  • How to create dashboard widgets.

Today, however, WordPress offers far more robust learning resources (e.g., the WordPress Plugin Handbook), making Hello Dolly’s educational role obsolete for most.

Cultural Significance#

Within the WordPress community, Hello Dolly has become a tradition. It’s a nod to the platform’s early days—a reminder of WordPress’s roots as a project built by and for enthusiasts. Longtime users often view it with affection, like an old friend.

Practical Use#

Here’s the catch: For 99% of WordPress users, Hello Dolly has no practical value. It doesn’t improve your site’s performance, security, or user experience. It doesn’t help with SEO, backups, or content management. It’s just… there.

Pros and Cons of Keeping Hello Dolly#

Let’s weigh the arguments for and against keeping Hello Dolly installed.

Pros#

  1. Nostalgia: For long-time WordPress users, it’s a fun throwback to the platform’s early days.
  2. Educational Example: For absolute beginners learning plugin development, it’s a simple code sample to study.
  3. Lightweight: It uses negligible server resources (we’ll dive deeper into performance later).

Cons#

  1. Dashboard Clutter: It takes up space in your admin dashboard, which can be distracting—especially if you use many widgets.
  2. Confusion for New Users: Beginners may wonder why a “useless” plugin is installed by default, leading to unnecessary questions.
  3. No Practical Benefit: It adds no value to your website or workflow.
  4. Unnecessary Attack Surface: Even simple plugins increase your site’s potential attack surface (though Hello Dolly is low-risk, as we’ll discuss).

Security Considerations: Is Hello Dolly a Risk?#

One of the biggest concerns with any plugin is security. So, is Hello Dolly a threat?

The Short Answer: Low Risk, but Not Zero#

Hello Dolly is maintained by the WordPress core team, which means it’s held to high security standards. It has very few lines of code, reducing the chance of vulnerabilities. To date, there have been no major security issues reported with the plugin.

That said, any plugin—even a simple one—increases your site’s attack surface. Hackers often target outdated plugins, and while Hello Dolly is rarely updated (its last significant update was in 2019), its simplicity means there’s little to exploit.

Should You Worry?#

For most users, Hello Dolly isn’t a security risk. But if you follow the principle of “least privilege” (only installing necessary plugins), it’s an unnecessary risk—however small.

Performance Impact: Does It Slow Down Your Site?#

Another common concern is performance. Does Hello Dolly slow down your WordPress site?

Front-End Impact: None#

Hello Dolly only runs in the admin dashboard, not on your site’s front end. Visitors will never experience lag or delays caused by it.

Back-End Impact: Minimal#

On the back end, Hello Dolly uses negligible resources:

  • PHP Execution: It runs a few lines of PHP to select a random lyric and display the widget. This takes milliseconds.
  • Database Queries: It doesn’t interact with your database at all.
  • Memory Usage: It loads a small array of lyrics (about 1KB of data) into memory.

In benchmark tests, Hello Dolly adds less than 0.01 seconds to dashboard load times. For most sites, this is undetectable.

Cumulative Effect#

While Hello Dolly alone won’t slow your site, every unnecessary plugin adds up. If you have dozens of unused plugins, their combined resource usage can affect admin performance. Hello Dolly is just one more drop in the bucket.

Should You Delete Hello Dolly? A Decision Guide#

Now, the million-dollar question: Should you delete Hello Dolly? The answer depends on your role and priorities.

For Beginners#

Recommendation: Delete It

If you’re new to WordPress, Hello Dolly serves no purpose. It clogs your dashboard, and you’re unlikely to benefit from its educational value (there are better learning resources available). Removing it simplifies your admin experience and teaches you to prune unnecessary plugins—a critical habit for site maintenance.

For Developers#

Recommendation: Delete It (Unless You’re Studying It)

If you’re a developer, you’ve likely already learned from Hello Dolly (or outgrown it). There’s no reason to keep it cluttering your dashboard unless you’re actively using it as a reference for a tutorial. Even then, you can re-install it temporarily.

For Website Owners#

Recommendation: Delete It

As a site owner, your goal is to optimize performance, security, and workflow. Hello Dolly offers nothing toward these goals. Deleting it reduces clutter, minimizes attack surface, and streamlines your dashboard.

For Nostalgic Users#

Recommendation: Keep It (But Be Aware)

If you love Hello Dolly’s nostalgia factor, there’s no harm in keeping it. Just remember:

  • It adds no value.
  • It uses minimal resources (so performance isn’t a concern).
  • It’s unlikely to ever cause security issues.

In short: Keep it if it makes you smile—but don’t feel guilty deleting it.

How to Delete Hello Dolly (Step-by-Step)#

Deleting Hello Dolly is as simple as removing any other plugin:

  1. Log in to Your WordPress Admin Dashboard.
  2. Navigate to Plugins > Installed Plugins.
  3. Locate “Hello Dolly” in the list of plugins.
  4. Click “Deactivate” (if it’s active).
  5. Once deactivated, click “Delete” (a red link below the plugin name).
  6. Confirm Deletion when prompted.

That’s it! Hello Dolly will be removed from your site.

Alternatives to Hello Dolly#

If you like the idea of a dashboard widget but want something more useful, consider these alternatives:

1. Custom Dashboard Widgets#

Build your own widget to display relevant info, like:

  • Recent sales (via WooCommerce).
  • Upcoming post deadlines.
  • Server status (e.g., disk space, memory usage).

Use a plugin like Dashboard Widgets Suite to create custom widgets without coding.

2. Productivity Plugins#

Replace Hello Dolly with widgets that boost productivity:

3. Fun (But Useful) Widgets#

For a mix of nostalgia and utility, try:

Conclusion#

Hello Dolly is a charming relic of WordPress’s past—a symbol of the platform’s roots as a community-driven project. Its simplicity and nostalgia have earned it a special place in the hearts of many users.

But when it comes to practicality, the verdict is clear: For most users, Hello Dolly offers no value. It clutters your dashboard, uses (minimal) resources, and adds unnecessary complexity to your site.

Final Recommendation: Delete Hello Dolly unless you have a specific reason to keep it (e.g., nostalgia). Your dashboard will be cleaner, your site slightly more optimized, and you’ll have one less plugin to worry about.

At the end of the day, WordPress is about building powerful, efficient websites. Hello Dolly, while endearing, doesn’t help with that.

References#

2025-11