Search "wordpress website designer" and the results blur two different jobs together. One person's portfolio is full of clean layouts built entirely in the block editor, nothing coded by hand. Another applicant sends a GitHub profile and talks about custom post types and plugin conflicts. Both will happily call themselves a WordPress person. They do different halves of the work, and paying for the wrong half is the most common way a WordPress budget gets wasted.
A WordPress website designer builds the layout, typography and visual system, usually inside the block editor or a page builder, without writing code. A WordPress developer writes PHP, custom blocks and integrations a builder cannot reach. Most new builds need a designer first. Most redesigns of an aging site need a developer involved from day one.
What does a WordPress website designer actually do?
A WordPress website designer works on the parts of the site a visitor actually experiences: page layout, typography, color, spacing, image direction and how the brand reads across the homepage, service pages and everything in between. In 2026 most of that work happens inside the block editor and the Site Editor rather than a separate design tool, since WordPress 7.0 made template parts, global styles and pattern-based layouts stable enough for real client work. A designer sets up theme.json, arranges reusable patterns, configures navigation and footer templates, and makes decisions about hierarchy and conversion paths, all without touching a line of PHP.
The edge of the role is the theme's own settings and block library. A capable WordPress designer can push a modern block theme a long way using native patterns, template parts and style variations, and that range has grown substantially since WordPress 7.0 shipped. What they typically should not be doing alone is editing template files directly, resolving a plugin conflict that breaks the checkout, or building a content structure the block editor was never designed to hold.
What does a WordPress developer do that a designer can't?
A WordPress developer works below the editor: PHP, JavaScript, custom blocks and plugins, custom post types and taxonomies, database queries, hooks and filters, and anything involving a third-party API. If a request starts with "can the site do something it currently can't," that is development work, not design work, no matter how visual the end result looks. WooCommerce logic beyond default settings, CRM or ERP integrations, custom caching for speed, and patching a security hole in an outdated plugin all sit with a developer.
Developers are also the ones who keep an existing site alive. Core and plugin updates land constantly, and each one carries a small chance of breaking something a designer has no way to diagnose, let alone fix. A designer without development skills genuinely cannot touch that layer, and a good one will say so rather than guessing at a code fix.
| Task | Designer | Developer |
|---|---|---|
| Block theme selection and Site Editor setup | Yes | Not their focus |
| Homepage and page layout | Yes | Only if custom code is required |
| Photography and content direction | Yes | No |
| Custom blocks or post types | No | Yes |
| Plugin conflicts and PHP errors | No | Yes |
| WooCommerce checkout logic | Rarely | Yes |
| API, CRM or ERP integrations | No | Yes |
| Site speed and Core Web Vitals fixes | Rarely | Yes |
| Security patching and core updates | No | Yes |
| Brand consistency across pages | Yes | Not their focus |
From-scratch build vs redesign: does the role change?
A brand-new site on a modern block theme is often design-led. Choose a solid theme, configure global styles, build out the page templates, and a developer's job shrinks to setup tasks such as hosting, staging, forms and a handful of custom blocks. Most small business builds fit this pattern comfortably, which is part of why WordPress website development projects on a clean slate tend to move faster than people expect.
A redesign of an existing WordPress site is a different job. There is a plugin stack that has grown for years, custom code nobody documented, content and URLs that have to survive the move without tanking rankings, and hosting quirks that only show up under real traffic. A developer needs to audit that technical debt before a designer commits to a new layout, because a page that looks great in a mockup can turn out to depend on a plugin the redesign was going to remove. Redesigns lean development-heavy earlier than new builds do, even though the visible outcome is design.
Before approving any redesign mockup, have a developer spend a day auditing the current plugin list, theme functions file and page speed scores. It is a few hundred dollars that routinely saves thousands, because it is much cheaper to learn a redesign assumption is wrong before the visuals are finished than after.
How much does each one cost in 2026?
US rates for both roles vary by experience more than geography, since most WordPress work happens remotely by default. Designers generally bill less per hour than developers at comparable seniority, though the gap narrows once a designer's work regularly involves conversion strategy rather than just layout.
| Engagement | WordPress designer | WordPress developer |
|---|---|---|
| Freelance, mid-level | $35 to $75 / hour | $60 to $120 / hour |
| Freelance, senior | $80 to $150 / hour | $100 to $200 / hour |
| Agency team, blended rate | $120 to $200 / hour, usually covering both roles | |
| Simple project, design only | $500 to $2,500 | n/a |
| Custom theme or plugin build | n/a | $6,000 to $25,000 |
Once a project needs actual development, whether that is a custom theme, WooCommerce logic or an integration, development hours usually make up most of the invoice, because testing and debugging take longer than layout decisions. Our own guide to hiring a WordPress developer goes deeper into project-level pricing, vetting questions and the maintenance costs that follow launch. If your build is a straightforward brochure site, our five-page website offer bundles design, build and copywriting for $1,700 instead of $3,000, which covers most of what a design-only engagement would otherwise cost separately.
Do you need both, or just one?
Work backwards from the actual request rather than the job title.
- If the problem is "this doesn't look right," it is a design problem. Layout, spacing, imagery and typography issues rarely need code.
- If the problem is "this doesn't work," it is a development problem. Broken checkouts, failed integrations and slow load times sit with a developer.
- If the problem is "we need something the theme has never done," it is development, even when the result is entirely visual. A custom quote calculator or a bespoke booking flow looks like design but gets built like software.
A new five to ten page site on a current block theme usually needs a designer first and a developer only for setup. A site with WooCommerce beyond the basics, membership logins, or a legacy redesign needs both roles budgeted from the start, even if the developer's early involvement is limited to an audit.
On redesigns we run the technical audit and the visual direction in the same week rather than one after the other. Sequential handoffs, where a design gets fully approved and only then goes to a developer who discovers the old theme can't support it, are the single biggest source of scope creep on WordPress redesign projects.
How do you tell them apart when you're vetting a hire?
Job titles on this platform are unreliable, so ask about the work instead. For a designer, ask whether they build in the native Site Editor or a page builder like Elementor, and check a live site of theirs on a phone rather than trusting a desktop screenshot. For a developer, ask about a recent plugin conflict they resolved and what changed after their typical build in PageSpeed Insights. For either, ask who owns the hosting, domain and code at handoff, since the correct answer is always you, on your own accounts.
Watch for a third category too: someone who installs a premium theme, drags blocks into a stock layout, and calls the result custom design. That work has a place for a fast, cheap brochure site, but it should not be priced like custom development, and it will not hold up once the business needs a feature the theme was never built to support.
Frequently asked questions
What is the difference between a WordPress website designer and a WordPress developer?
A WordPress website designer works on layout, typography, brand and page structure, usually inside the block editor or a page builder, without writing code. A WordPress developer writes PHP, JavaScript and custom blocks, builds custom post types, fixes plugin conflicts, and handles integrations and performance work a designer cannot reach. Designers decide how the site looks. Developers decide what it can actually do.
Do I need a WordPress developer or a designer for a new site?
A new brochure site on a modern block theme usually needs a designer first, since WordPress 7.0's Site Editor handles layout, navigation and templates without code. You need a developer up front only if the build requires custom functionality a theme cannot do natively, such as a custom booking flow, membership logic, or a non-standard WooCommerce checkout.
How much does a WordPress website designer cost in 2026?
US-based WordPress designers typically bill $35 to $75 an hour at the mid level and $80 to $150 an hour for senior specialists, with simple design-only projects running $500 to $2,500. WordPress developers bill somewhat higher, commonly $60 to $150 an hour, because custom builds carry more testing and integration time.
Is a WordPress redesign a design job or a development job?
Usually both, but a redesign leans development-heavy earlier than a new build does. An existing site carries plugins, custom code, content and URLs that all have to survive the move. A developer should audit the technical debt before the designer finalizes a new layout, or the redesign gets constrained by problems nobody found until week six.
Can one person do both WordPress design and development well?
Sometimes, and many freelancers advertise as full-stack WordPress people. A hybrid generalist is a reasonable fit for a small site on a stock block theme with light customization. Once a project needs a distinctive design and real custom functionality at the same time, two specialists or an agency covering both usually outperforms one generalist stretched across both jobs.
Should I hire a WordPress designer or just use a page builder myself?
Doing it yourself is fine for validating a business or a very simple site where you have the time. A hired designer earns their fee once the site needs to convert visitors, since they think about page hierarchy, trust signals and mobile behavior in ways a DIY build built from a demo import rarely does. The gap shows up in conversion rate, not appearance.
The takeaway
Stop hiring by job title and start hiring by the problem you actually have. A site that looks wrong needs a designer. A site that doesn't do something it needs to do needs a developer. A redesign of an aging site needs a developer involved before the design gets finalized, not after. Get that sequencing right and the rest of the hiring decision, including the budget, sorts itself out.