Web developer hourly rate calculator
Developers mostly sell fixed-price builds and day-rate contracts, so the hourly rate stays invisible — until a project overruns and there is no floor to measure the damage against. This calculator makes the number explicit: the rate your income, costs and real billable hours require.
The pricing reality for freelance developers
Development work is sold three ways, and each one leans on the hourly rate differently. Fixed-price builds — a marketing site, an e-commerce store, an MVP — are really hour estimates wearing a disguise: quote 80 hours at a rate you have never calculated and the project is a coin flip. Day rates dominate contract work, often through agencies, and the trap there is comparing your day rate with a salaried developer's daily cost, which quietly excludes holidays, tax and the weeks between contracts. Retainers and maintenance agreements are the third model: steady income, but support requests arrive in fragments that are hard to log and easy to give away.
The non-billable load in development is distinctive. Environment setup, dependency wrangling and deployment plumbing precede the first visible feature. Debugging someone else's legacy code runs at half speed for reasons that are nobody's fault. Meetings and stand-ups multiply as soon as you work with a team. And the stack will not sit still: a meaningful slice of every month goes on learning the framework version, platform change or tooling your next project will assume you know. Developers in steady contract work can bill a higher share of their week than most trades, which is why the preset here stays at 60% — but developers hopping between small projects often find 50% closer to the truth, and the honest number is the one your timesheets show.
The presets below — a $95,000 target income, $3,600 a year of expenses, 60% billable time — produce a rate near $126 an hour. Treat that as the measuring stick, not a market claim: fixed quotes get built from it, day rates get compared against eight times it, and retainers get checked so the effective rate does not quietly slide below it when "quick questions" accumulate.
Your numbers — developer presets
Your recommended rate
| Income + expenses needed | $0 |
| Grossed up for tax | $0 |
| With profit margin | $0 |
| Working weeks | 0 |
| Total working hours | 0 |
| Billable hours | 0 |
Your rate is saved on this device only, so the Proposal Generator can show it when you price a project.
Costs developers forget to put in the rate
- Hosting, staging and test infrastructure. Your own servers, staging environments, CI minutes and the test domains and services projects run on before launch — small bills, every month, rarely invoiced to anyone.
- Licences and tooling. IDE subscriptions, component libraries, plugins and monitoring tools renew quietly in the background of every project.
- Test devices. The spare phone, the older laptop, the browser matrix you actually test on — keeping a realistic device shelf is a business cost, not a hobby.
- Staying current. Courses, documentation time and the unpaid week spent learning a new stack before a client will pay you to use it. The learning is unavoidable; whether the rate funds it is a choice.
- The replacement cycle. A development machine on a three-to-four-year cycle is one of your largest costs. Smoothed across the year it belongs in the expenses figure, not in a bad month's panic.
How this calculator works
Start with the hours you can genuinely sell. Take 52 weeks, subtract your vacation weeks, multiply by your hours per week, then multiply by your billable percentage. With the developer presets — four weeks off, 40 hours a week, 60% billable — that is 1,152 billable hours a year. Setup, meetings and learning come out of the other 768; if your real split is worse than that, lower the percentage and let the rate rise.
Next, add your desired income and annual expenses, gross the total up for tax by dividing by one minus your tax rate — at 25%, divide by 0.75 — then add your profit margin and divide by billable hours. The result is the rate a fixed-price quote has to be built from if the project is going to pay like a job rather than a gamble.
For a build quote, the working method is: estimate hours honestly (then look at your last three projects and correct for how those estimates actually went), multiply by this rate, and add a contingency line for the unknowns every build contains. If the client's budget cannot meet that number, the professional move is to cut scope — not to cut the rate and hope the overrun fairy is kind.