How Much Do Web Developers Charge in 2026? Hourly Rates and Project Prices

How much do web developers charge per hour? One published reference is Arc’s web-development rate page, which displays a $61–$80/hour band for both average and median. This global, all-experience-level platform page is not a representative survey of the whole market or a new 2026 study. Sources checked September 22, 2026; all prices below are USD. A fixed website quote needs a defined scope, not just an hourly benchmark.

Do not confuse a wage with a contractor invoice. The U.S. Bureau of Labor Statistics reports a $92,650 median annual wage for web developers in May 2025. That is employee pay, not a freelance hourly quote: a contractor prices a service and its business costs. Neither source fixes your project budget. For finished-site pricing, see the website cost guide; here, compare engagement models, responsibilities and written estimates.

The four ways developers charge

First ask what triggers a bill: time worked, agreed deliverables, reserved capacity or negotiated business value. Choose a model whose scope and approval rules you can manage:

• Hourly. Pay the agreed rate for recorded work. Useful when investigation must precede an estimate, such as debugging an existing site. Request a task-level estimate, a spending cap and approval before exceeding it. Confirm whether meetings and reporting are billable.
• Fixed project price. Pay an agreed amount for written deliverables. Identify templates, features, revision rounds and acceptance tests before signing. A fixed fee does not make additional work free: define how both parties approve scope changes and revised prices.
• Monthly retainer. Reserve defined hours or services, such as a website maintenance plan. Specify response targets, covered systems, unused-hour rules and extra-work rates. A retainer is not automatically unlimited support or round-the-clock availability.
• Value-based pricing. Negotiate a fee informed by the project’s value to the business rather than timesheets alone. Require written deliverables and acceptance criteria here too. Forecast revenue is an assumption, not evidence that the website will produce those sales.

Web developer hourly rates: benchmark, role and scope

Use the published band as a reference point, then ask what each quote covers. Job titles are not standard price brackets. Review relevant work and the responsibilities below; neither seniority nor an agency label proves quality, speed or the hours your project needs. Because the published figures are bands, do not turn their midpoint into an exact average. A useful quote should name the person doing the work and the assumptions behind their estimate.

• Junior freelancer. Ask which tasks they complete independently and who reviews the work. A small paid milestone with agreed tests can establish fit for a contained change without committing the whole budget.
• Mid-level freelancer. Confirm responsibility for design, implementation and launch. Ask for relevant WordPress or custom-site work and a demonstration of the features you need, rather than relying on a title.
• Senior freelancer / specialist. For web applications, integrations or recovery work, identify the technical risk. Request an estimate separating investigation, implementation and testing; do not assume an automatic time saving.
• Agency team. Ask who handles design, development, project management and quality assurance. Request a blended rate or breakdown by role, and check for overlapping charges. Team size alone neither establishes value nor justifies rejecting a quote.
• Web designer. Clarify whether the fee buys layouts, a prototype, a working site or both design and development. Content, asset licensing and handoff files need owners too; use the candidate-vetting checklist to confirm responsibilities.

Comparing developer quotes across countries

Country affects currency, contracting arrangements and working-hour overlap; it does not tell you what an individual developer will charge. These are practical comparison checks, not country-average rates. Ask each supplier for the same deliverables before converting prices:

• United States / Canada: confirm whether a dollar quote means USD or CAD. Separate the subtotal, applicable taxes and transaction charges before comparing converted totals.
• UK / Western Europe / Australia: specify the actual invoice currency, such as GBP, EUR or AUD. Agree an exchange-rate date and check whether relevant taxes are included.
• Eastern Europe (Poland, Ukraine, Romania): these are separate countries, not one price market. Confirm each supplier’s billing currency, contracting entity and support window.
• South Asia (India, Pakistan, Bangladesh): agree shared working hours and written approvals. Evaluate the individual team’s relevant work; a region label establishes neither quality nor price.
• Southeast Asia (Philippines, Vietnam): set handoff times, response expectations and the language of deliverables. Include payment-platform and currency-conversion fees where they apply.
• South Africa / Nigeria / Kenya: confirm the contracting party, invoice currency and payment terms for each provider. Compare identical scope and acceptance criteria, not an assumed regional average.

These checks apply to domestic and overseas suppliers alike. For remote work, agree review times and an escalation contact, and ask how handover will work if the relationship ends. Evaluate demonstrated work, communication and process using how to hire a web developer, rather than assuming a location guarantees savings or capability.

From hourly rate to total website cost

The following are hypothetical labour calculations, not standard hours required or typical market totals. Unless explicitly included, budget separately for hosting, domains, content, licensed assets, paid plugins, taxes and approved changes. For a first-year comparison, include 12 months of recurring services and distinguish one-off setup fees from renewals. Put optional items on separate lines. Ask the estimate to identify design, content entry, QA/testing and handover:

• Landing page: assume 30 hours × $60/hour = $1,800. Define sections, supplied copy, form behaviour and revision limits before accepting the estimate. Choose the scope using landing page vs website.
• Small business website: assume 60 hours × $60/hour = $3,600. State the page count and unique templates; compare the website cost guide and distinguish working hours from elapsed time in website timelines.
• E-commerce store: assume 80 hours × $75/hour = $6,000. Define catalog size, product entry, payment and shipping setup, and test purchases. Check additional scope in the e-commerce cost guide.
• Web application / portal: assume 160 hours × $75/hour = $12,000. Specify roles, workflows and integrations before relying on that allowance; use web app development cost to identify requirements that need estimating.
• Redesign: assume 40 hours × $60/hour = $2,400. Check existing templates, URL redirects and content migration before estimating. The redesign cost guide helps separate a visual refresh from a rebuild.
• Per-page quotes: ten pages at an assumed 2 hours each, plus 15 shared setup/testing hours, make 35 hours: 35 hours × $60/hour = $2,100. Use page-count planning, then price unique features separately.

Request a separate allowance for ongoing maintenance, including updates, backups and recovery. Promotion is separate work too: compare SEO budgeting and traffic-building options against a defined plan. A development fee does not buy guaranteed visitors, rankings or enquiries.

Compare hourly quotes for the same scope

For the same written scope, one hypothetical quote estimates 40 hours × $50/hour = $2,000; another estimates 25 hours × $80/hour = $2,000. Different hourly rates, identical labour totals. Neither estimate proves better skill or delivery. Check whether both include design, revisions, QA and handover:

• Effort assumptions. Ask for hours by task and explanations of large differences. If one quote omits testing or assumes supplied content, it is not yet a like-for-like comparison.
• Scope of skill. Make mobile behaviour, form delivery and performance checks explicit. The website usability guide and speed-problem guide can inform that checklist; a higher rate alone does not demonstrate these skills.
• Process. Identify the reviewer, staging environment, backup process and handover documents. Establish how milestones are accepted and how defects are distinguished from requests for new features.
• Availability. Confirm start dates, review deadlines and expected working hours. A rate tells you neither the supplier’s availability nor how quickly your team can provide content and approvals.

Resolve missing items before negotiating. A detailed lower quote can be appropriate; a higher one may include work you need. If a builder is another option, compare editing effort and limitations using AI website builder vs developer rather than assuming either route is cheaper.

A written checklist for a fair web development quote

Turn the chosen estimate into an agreement you can both check. These six items make the price, handover and definition of done inspectable:

1. 1Written deliverables. List pages, templates, features, content responsibilities, exclusions and revision rounds. Give each milestone an output you can review; settle unresolved requirements before treating an estimate as a fixed commitment.
2. 2Acceptance tests. Include a test form submission with confirmed delivery, mobile layout checks and keyboard/accessibility checks on agreed browsers and devices. For the form, specify required fields, invalid-input handling, the destination inbox and who verifies delivery. State what must be fixed before acceptance; a screenshot alone is not proof.
3. 3Price and change control. Record currency, taxes, payment milestones, the rate cap and total spending limit. For hourly work, require a task log; for extra work, approve change orders and their cost in writing before implementation. Record whether the estimate is a ceiling or forecast, and when you will receive progress and budget updates.
4. 4Staging and baselines. Review changes away from the live site where possible. For redesigns, record existing URLs and available performance measurements, agree backup and rollback steps, and compare the same pages under documented test conditions.
5. 5Ownership and licensing. Keep domain and hosting accounts under your control. Specify when code, content, design files and credentials are handed over, plus third-party licences, renewals and reuse restrictions. Ownership promises cannot override those licences.
6. 6Support and communication. Agree who signs off, how issues are reported, response targets and the duration and scope of post-launch support. Use the hiring guide to check these terms before paying.

Three illustrative web development budgets

These are illustrative scopes, not real client budgets or portfolio results. Rates and hours are assumptions, not country averages, recommended rates or delivery promises. Replace them with your supplier’s task estimates:

• Illustrative starter scope: 20 hours × $45/hour = $900. Assume a template-based site with four content pages, supplied text and images, one enquiry form and one revision round. Include configuration, content entry, mobile checks, a form-delivery test and handover. Confirm the supplier can cover those tasks within the allowance; custom branding, copywriting and integrations are excluded, and recurring services are extra.
• Illustrative service-business scope: 60 hours × $60/hour = $3,600. Assume six pages using agreed templates, supplied copy, an enquiry form and editing guidance. One possible breakdown: briefing 6 hours, design 12, implementation 24, QA 12 and handover 6, totalling 60 hours. Agree which accessibility and performance checks fit inside QA; extra templates, copywriting, paid licences and ongoing support need separate prices.
• Illustrative portal phase: 160 hours × $75/hour = $12,000. Assume sign-in, two user roles, one workflow and a simple admin view. Request explicit permissions, validation, error handling, testing and deployment tasks. Data migration, billing, integrations or broader security review may change scope and must be estimated separately. This defines a hypothetical phase, not proof that every portal fits the allowance.

Move optional features into a separately priced later phase if necessary; do not remove essential access controls or testing to match an example total. If discovery exposes more work, compare a smaller launch, a revised budget or another approach before authorising it.

The bottom line

There is no single fair web developer rate for every buyer. Arc provides one published platform reference; your decision needs a written scope, an explained effort estimate, acceptance tests and a full cost breakdown. Compare the same deliverables and recurring-cost period, clarify exclusions and document change approvals. That is more useful than choosing the lowest hourly figure or treating a title as proof of quality.