Freelance rate vs salary: why a $60,000 job isn't $30 an hour
Last updated: July 2026
The most expensive mistake in freelancing takes ten seconds to make. Take the salary you'd accept, divide by 2,000 working hours, quote the result. $60,000 becomes $30 an hour, the client agrees instantly (they should, it's a bargain), and the whole year quietly runs at a loss compared to the job you left.
In short: dividing a salary by 2,000 hours is the most expensive mistake in freelancing; the honest converted rate is closer to double, because a salary silently includes benefits, off time and a full billable year nobody has.
The honest conversion is closer to double that. Here's where the difference hides.
What a salary silently includes
A salary is not a price for hours. It's a package, and most of the package is invisible until you have to buy it yourself.
Paid vacation and holidays: you earn during weeks you don't work. Sick days that don't dent your income. Employer-paid contributions, insurance, often a pension match, all paid on top of your gross. A laptop, software, an office, training. And the biggest one, because nobody ever lists it: guaranteed utilization. An employee never spends Tuesday hunting for someone to buy Wednesday.
A freelancer buys every item on that list out of their rate. That's the entire mystery of why freelance rates look "expensive" next to salaries: they're carrying cargo the salary never shows.
The quick conversion
A salaried year is ~2,080 paid hours. A realistic freelance year is ~1,100 billable hours. Same income goal, roughly half the hours to carry it: before benefits and costs, your break-even hourly is already about double the salary math.
Run the honest numbers
Do the division with real numbers. 25 billable hours a week, 47 working weeks: about 1,100 billable hours a year. $60,000 spread over those is already $55 an hour, and that's before you've bought back a single benefit or paid for your own laptop. Add costs, taxes handled freelancer-style, and a margin for slow months, and the ladder below tells you what actually replaces that job.
Type the monthly equivalent of the salary you'd accept as your Target Pay, and set your real availability.
Target rate
Target Pay
desired monthly income, before tax
Monthly Costs
monthly costs to stay afloat
Billable hours
billable hours per week
Weeks off
vacation, holidays, sick days
Drag any blue number to adjust (click it to type). Your inputs carry over to the full tool. Access full tool
The comparison that actually matters
Rate vs salary is the wrong duel anyway. The real trade is take-home plus freedom against take-home plus security, and both sides are legitimate.
A freelance rate that only matches your old salary is a pay cut with paperwork.
The salary buys you predictability: same number every month, someone else worries about the pipeline.
The rate buys you the upside: every efficiency you gain is yours, every rate raise compounds, and your calendar belongs to you (mostly).
What the rate must never do is match the salary's number while dropping the salary's protections. That's the $30-an-hour trap from the first paragraph.
When the salary honestly wins
Some situations genuinely favor employment, and pretending otherwise is coach talk. If your pipeline can't fill 20 billable hours a week yet. If your runway is under three months. If the benefits you'd have to replace are unusually expensive where you live. A salary is a fine instrument; it's just not a unit of measurement for freelance pricing.
If you're doing the comparison for real, do it with your own numbers, not with a rule of thumb from an article, including this one.
What replaces your salary?
Type the salary you'd accept as your target pay. The ladder shows the rate that actually carries it.
Run my numbersFree, no signup. For real.
Read next
How many billable hours per week is realistic? →The 1,100-hours-a-year claim, defended. It decides half of this comparison.