Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Setup & site building · Info

Is WordPress Frontend or Backend? The Short Answer

Is WordPress Frontend or Backend? The Short Answer

Short answer

WordPress is both frontend and backend. Its PHP code and database run on the server as the backend, while themes output the HTML, CSS and JavaScript that visitors see. In everyday use, people also call the admin dashboard the backend and the public site the frontend.

Key takeaways

  • WordPress is a full-stack CMS covering both sides.
  • PHP and the database form the technical backend.
  • Themes and blocks produce the frontend visitors see.
  • Users often call the admin dashboard the backend.
  • Headless setups use WordPress as a backend only.

Is WordPress frontend or backend?

WordPress is both: its PHP code and MySQL or MariaDB database run on the server as the backend, and its themes produce the HTML, CSS and JavaScript that visitors see as the frontend.

That makes WordPress a full-stack content management system. It handles storing content, managing users and building pages, then sends finished pages to the browser.

The confusion comes from the word backend. WordPress users often call the admin dashboard the backend, while developers use the word for server-side code. Both meanings are covered below.

WordPress's server side runs on PHP, and the PHP manual is the official reference for the language.

What do frontend and backend mean in web development?

The frontend is everything that runs in the visitor's browser, and the backend is the code, database and server logic that run before the page is sent.

Frontend code is mainly HTML for structure, CSS for styling and JavaScript for interaction. The MDN guide to how the web works shows how a browser requests pages from a server.

Backend code runs on the web server. It reads and writes data, checks who is logged in and assembles pages.

A simple way to remember it: the frontend is what you see, and the backend is what makes it work.

Some teams also talk about full-stack developers, meaning people who work on both sides. WordPress sits in that full-stack space because one install covers storage, logic and display.

Which parts of WordPress are backend?

The WordPress core PHP files, the database, plugins' server-side logic, user accounts, the REST API and the admin dashboard's processing all belong to the backend.

WordPress is written mostly in PHP, a server-side language. The PHP manual describes PHP as a general-purpose scripting language suited to web development that runs on the server.

Content lives in a MySQL or MariaDB database. The WordPress requirements page lists the PHP and database versions it recommends.

When someone visits a post, PHP queries the database, loads the theme and builds an HTML page. All of that happens before anything reaches the browser.

Which parts of WordPress are frontend?

The pages visitors see, built from your theme's templates, styles and scripts, plus the JavaScript-powered block editor interface, are the frontend parts of WordPress.

Your theme controls the public look of the site. It outputs HTML and loads CSS and JavaScript files.

Blocks also have frontend output. A Gallery or Navigation block includes markup and sometimes scripts that run in the visitor's browser.

The block editor itself is a large JavaScript application built with React. So even the admin area has a big frontend component, just one that only logged-in users see.

What do WordPress users mean by “the backend”?

In everyday WordPress talk, the backend means the admin dashboard at /wp-admin/, where you write posts, install plugins and change settings, while the frontend means the public site.

This is a user-facing meaning, not a technical one. When a support article says go to the backend, it means log in to the dashboard.

You reach it by adding /wp-admin/ or /wp-login.php to your domain. Our guide on the WordPress admin URL explains the options.

Technically, the dashboard itself has both sides. Its screens are rendered in your browser, while the actions you take are processed by PHP on the server.

How does a WordPress page get from backend to frontend?

The browser requests a URL, PHP loads WordPress, queries the database for the matching content, runs the theme template and sends back finished HTML for the browser to display.

Here is the flow in order:

  1. A visitor requests a page.
  2. The web server passes the request to PHP.
  3. WordPress loads core, plugins and the active theme.
  4. WordPress queries the database for the content.
  5. The template hierarchy picks the right template.
  6. The finished HTML is sent to the browser.
  7. The browser loads CSS, JavaScript and images and shows the page.

Page caching can skip steps 2 to 6 by serving a saved copy. Our guide to page cache vs object cache explains how that speeds things up.

How do the parts compare?

The table below sorts the main pieces of WordPress into frontend and backend so you can see where each one runs.

Part of WordPressFrontend or backendWhere it runs
Core PHP filesBackendWeb server
Database (posts, users, settings)BackendDatabase server
REST APIBackendWeb server
Theme templates and stylesFrontend outputBuilt on server, shown in browser
Block editor interfaceFrontendBrowser (JavaScript)
Admin dashboardBothBrowser screens, server processing
PluginsUsually bothServer logic plus browser scripts

Most plugins touch both sides. A contact form plugin shows a form in the browser and saves or emails entries on the server.

Knowing which side a problem lives on saves time when troubleshooting. A layout glitch that only appears in one browser points to frontend code, while a white screen or database error points to the backend.

Browser developer tools help with frontend issues. Server error logs and the WordPress debug log help with backend issues, as our guide on how to enable debug mode explains.

Can WordPress be used as backend only?

Yes, WordPress can run as a headless CMS, where it only stores and serves content through the REST API or GraphQL, and a separate frontend built with a framework like Next.js displays it.

The REST API Handbook documents the endpoints that let other apps read and write WordPress content as JSON.

In a headless setup, your theme is mostly unused. Editors still use the familiar dashboard, but visitors see a site built in another tool.

This suits teams that want a custom JavaScript frontend or need to feed content to apps. It adds complexity, so read our comparison of headless WordPress vs traditional before choosing it.

Is WordPress a good skill for frontend or backend developers?

WordPress is useful for both: frontend developers build themes and blocks with HTML, CSS, JavaScript and React, while backend developers write plugins, custom endpoints and database logic in PHP.

Theme and block developers spend most of their time on frontend skills, plus a little PHP. Block development in particular leans heavily on modern JavaScript.

Plugin developers work mostly in PHP and SQL. They also handle security tasks such as escaping output and checking permissions.

If you want to try block work, our guide on how to create a custom block in WordPress is a practical starting point.

Do you need to code to use WordPress?

No, most site owners never touch the code, because the dashboard, block editor, themes and plugins let you build and run a site without writing frontend or backend code.

You only need code when you want something no theme or plugin offers. Even then, small changes often involve a few lines of CSS.

Knowing the difference between frontend and backend still helps. It tells you where to look when something breaks, such as a styling issue versus a server error.

For a plain-language overview of the platform, see what WordPress is in simple words.

Frequently asked questions

Is WordPress a backend framework?

Not exactly. WordPress is a content management system rather than a general framework like Laravel. It does give developers backend tools such as hooks, a database layer, user roles and the REST API, so many people build custom features on it as if it were a framework.

What language is the WordPress backend written in?

The WordPress backend is written mainly in PHP and stores data in a MySQL or MariaDB database. The block editor and many admin screens use JavaScript and React, which run in the browser rather than on the server.

Is the WordPress dashboard the frontend or the backend?

In WordPress terms, the dashboard is called the backend because it is the private admin area. In technical terms it has both parts: screens drawn in your browser and actions processed by PHP on the server.

Can I use React with WordPress?

Yes. The block editor is built with React, so custom blocks are usually written in React. You can also build a separate React or Next.js frontend that pulls content from WordPress through the REST API or GraphQL in a headless setup.

Sources

  1. Requirements WordPress.org
  2. REST API Handbook WordPress Developer Resources
  3. How the web works MDN Web Docs

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.