Freelance Technical Writer Rates
US freelance technical writers charge $55–$150/hr, with API and SDK documentation at the top of the range and help-center work at the bottom. The calculator below is preset to technical-writing defaults — pick your deliverable, experience, and industry to land on a real number, then read the per-page, per-word, and SaaS-vs-hardware tables underneath.
Calculate Your Technical Writing Rate
REST/GraphQL reference, endpoint guides, code samples
+15% — high demand, fast release cycles, well-funded budgets
Recommended hourly rate
$75 — $173/hr
Est. 15 hrs for 3,000 words = $1,635 at midpoint
Rates by Deliverable Type
| Deliverable | Per Word | Per Page | Hourly |
|---|---|---|---|
| API Documentation | $0.4-$1.2 | $90-$280 | $65-$150/hr |
| SDK / Developer Guide | $0.4-$1.1 | $90-$260 | $65-$145/hr |
| User Manual / Guide | $0.25-$0.8 | $60-$200 | $55-$120/hr |
| Knowledge Base / Help Center | $0.2-$0.6 | $45-$150 | $50-$105/hr |
| White Paper / Technical Article | $0.4-$1.5 | $100-$350 | $70-$175/hr |
| SOPs / Process Docs | $0.2-$0.7 | $50-$160 | $50-$110/hr |
US market rates for mid-level technical writers, before industry and experience adjustments. API and SDK documentation carries a premium because it requires reading code and validating samples.
Which Pricing Model Should You Use?
Hourly
Best for: evolving products, SME-dependent work, doc maintenance. Protects you when scope is unknown up front — common in early-stage SaaS.
Per Page
Best for: manuals and structured docs where page count is predictable. Define a page (≈250 words) in the contract so screenshots and code blocks don't inflate the count.
Per Word
Best for: knowledge-base and help-center articles with clean source material. Penalizes the concise, well-structured writing technical docs actually need.
Per Project
Best for: a defined doc set (a full API reference, a release's docs). Rewards speed and tooling — the most profitable model once you can estimate scope reliably.
Hourly Rates by Experience Level
Experience drives the rate more than any other single factor, because senior writers need fewer SME cycles and produce docs that ship with less review.
| Level | Experience | Hourly | What clients expect |
|---|---|---|---|
| Entry | 0–2 yrs | $45 – $70 | Drafts to a template, needs editorial review |
| Mid | 3–6 yrs | $65 – $100 | Owns a doc set, runs SME interviews independently |
| Senior | 7–12 yrs | $90 – $150 | Docs-as-code, information architecture, style governance |
| Principal | 12+ yrs | $130 – $200+ | Docs strategy, tooling, and content-ops consulting |
What a $75/hour technical writer is actually doing
SOPs and runbooks for a general-industry client, five years' experience, a 4,000-word set of procedures — the calculator above, prefilled:
Load the $75/hr scenario →It returns $50–$110/hr, midpoint $75, and estimates 20 hours for the set — about $1,500. That is the honest middle of process documentation: the writing is fast, but the value is capped by what the procedures are worth to the client.
Now compare it to the view this page opens on — API documentation, SaaS, the same five years — which starts at $75/hr and runs to $173. Same writer, same seniority: $75 is your midpoint on SOPs and your floor on an API reference. Changing what you document moves your rate further than another two years of experience does.
Swap industry=saas in the URL and the same SOP work becomes $57–$126/hr — the premium is for the release cadence, not the deliverable.
Per-Page & Per-Word Rates: API Docs vs. User Manuals
API documentation is the most valuable deliverable a freelance technical writer produces, because it requires reading code, calling endpoints, and keeping samples accurate. User manuals pay less per unit but tend to be longer, so the project totals are comparable.
| Deliverable | Per Word | Per Page (~250 words) | Typical Project |
|---|---|---|---|
| API documentation | $0.40 – $1.20 | $90 – $280 | $3,000 – $15,000 (full reference + guides) |
| SDK / developer guide | $0.40 – $1.10 | $90 – $260 | $2,500 – $10,000 |
| User manual / guide | $0.25 – $0.80 | $60 – $200 | $2,000 – $8,000 |
| Knowledge base / help center | $0.20 – $0.60 | $45 – $150 | $75 – $300 per article |
| White paper / technical article | $0.40 – $1.50 | $100 – $350 | $3,000 – $7,000 |
A “page” is ~250 words of running text. Define it in the contract so screenshots, code blocks, and tables don't inflate a per-page count.
SaaS vs. Hardware Industry Rate Tables
The same deliverable pays differently across industries. SaaS documentation carries a premium for fast, continuous release cycles and well-funded budgets; hardware and embedded work pays a smaller premium but is steadier and often regulated.
SaaS / Software (mid-level hourly)
| Deliverable | Hourly |
|---|---|
| API documentation | $75 – $170 |
| SDK / developer guide | $75 – $165 |
| Knowledge base / help center | $58 – $120 |
| Release notes / changelog | $58 – $115 |
Hardware / Embedded (mid-level hourly)
| Deliverable | Hourly |
|---|---|
| Firmware / API documentation | $70 – $160 |
| Installation / service manual | $60 – $130 |
| User manual / guide | $58 – $128 |
| SOPs / compliance docs | $54 – $118 |
Regulated hardware (medical devices, aerospace, automotive) can match or beat SaaS rates when the work demands standards fluency (IEC 62304, ISO 9001, DITA structured authoring).
Technical Writer vs. Copywriter vs. Translator Rates
These three roles sell writing by the word to overlapping clients, and their rates are set by completely different things. Worth knowing before you take the adjacent job, or quote it.
| Role | Per word | Hourly | What sets the rate |
|---|---|---|---|
| Technical writer | $0.20 – $1.20 | $55 – $150 | The cost of extracting the information — SME interviews, reading code, running the thing you're documenting |
| Copywriter | $0.08 – $1.50 | $50 – $200 | Revenue the words are credited with. Content sits at the bottom of that range, conversion copy at the top |
| Translator | $0.08 – $0.32 | $35 – $85 | Scarcity of the language pair and subject, against a source text that fixes the word count for you |
The comparison that matters is per hour, not per word. A copywriter on a sales page can beat any technical writing rate per word, because the client is buying attributable revenue rather than accuracy — but that work is won on portfolio results, not on knowing the product. Technical writing pays a narrower, steadier band, and it pays it whether or not the last thing you wrote converted.
Documentation localization is where the roles actually meet. If your docs are being shipped in eight languages, the translators downstream are working from your source text, and every ambiguous sentence you leave gets paid for eight times. Writers who can structure docs for translation — consistent terminology, no idioms, short declaratives, a maintained glossary — bill the setup as its own engagement rather than absorbing it into the page rate.
Moving between the three is easiest in the direction of the subject matter you already have. A technical writer who understands the product can write its launch copy; a generalist copywriter usually cannot write its API reference. That asymmetry is the argument for your rate when a client compares your quote to a content agency's.
How to Price Technical Writing Projects
Most underpricing comes from quoting before scope is clear. Work through these steps before you send a number:
- Start from your hourly floor. Whatever model you quote, back-solve it against a real hourly rate so a fixed fee never drops below what your time is worth. The freelance rate calculator gives you that floor after tax, insurance, and non-billable time.
- Audit what already exists. An API with an OpenAPI spec and inline comments is half documented; a product with nothing but a Slack thread is not. Price the gap, not the page count.
- Estimate SME load.Technical writing is interview-bound. Two hours of engineering time per 1,000 words is normal early on; quote hourly until you know the team's responsiveness.
- Pick the model that protects margin. Hourly for unknown scope, per page for predictable manuals, per project once you can estimate a doc set. Avoid per-word for anything that rewards brevity.
- Add a maintenance line. Docs rot. A monthly retainer to keep references in sync with releases is recurring revenue most writers leave on the table.
- Bill tooling and structure separately. Setting up docs-as-code, a static-site generator, or DITA/structured authoring is a distinct project from writing — price it as one.
Recommended gear
Tools technical writers use
The toolchain is mostly free — a Markdown editor, a static site generator, a prose linter like Vale. What you buy is the style guide the linter enforces, the usage references you cite when a reviewer disagrees with an edit, and the standard texts on the craft. Affiliate links — buying through them helps fund this calculator.
The Chicago Manual of Style (18th ed.)
University of Chicago Press
The fallback authority when a client has no house style. Worth owning for one reason: "Chicago says" ends an editing argument that would otherwise cost you an unbilled hour.
Microsoft Manual of Style (4th ed.)
Microsoft Corporation
The print predecessor of the free Microsoft Writing Style Guide, and still the deeper reference for UI terminology and procedure writing. Half of software docs work is written to some descendant of this book.
Read Me First! A Style Guide for the Computer Industry (3rd ed.)
Sun Technical Publications
The other house style clients inherit. Strongest on task-based procedures, code conventions, and the parts of a doc set — the questions that come up on day one of a new engagement.
Docs for Developers
Bhatti, Corleissen, Lambourne, Nunez & Waterhouse
The practical field guide to developer documentation — planning, drafting, sample code, and measuring docs. The closest thing the field has to a standard text, and the fastest route into API work.
Modern Technical Writing
Andrew Etter
Ninety minutes on docs-as-code: Markdown, static site generators, and version control instead of a CMS. The argument you'll make to a client for billing the toolchain setup as its own project.
Every Page Is Page One
Mark Baker
The book that reframed help content for search-first readers. Essential for anyone writing a modern knowledge base, where every article has to work as someone's first page.
Developing Quality Technical Information (3rd ed.)
Carey, Lanyi, Longo, Radzinski, Rouiller & Wilde (IBM Press)
IBM's nine quality characteristics, with before-and-after examples. The most useful thing on this shelf for defending a rewrite to an engineer who liked their original draft.
Dreyer's English
Benjamin Dreyer
Grammar and usage from Random House's copy chief. The reference that resolves the comma and hyphen questions a client's reviewer will raise, without reading like a rulebook.
Dell U2723QE 27" 4K USB-C
Single-cable monitor
Docs work is editor + API console + rendered preview side by side. A 4K panel with a USB-C hub keeps all three readable at once.
The Wealthy Freelancer
Slaunwhite, Savage & Gandia
The client-getting system, which is what lets you decline the $40/hr help-center job without flinching. Business side, not craft.
As an Amazon Associate this site earns from qualifying purchases. Links are sponsored.
Related Calculators & Guides
Freelance Rate Calculator
Calculate your minimum hourly rate
Copywriter Rates
Per-word, per-project, and hourly copywriting rates
Translator Rates
What the docs you write pay downstream, by language pair
Web Developer Rates
Hourly and project rates by stack and experience
Writing Rates Per Word
2026 per-word benchmarks across writing niches
Frequently Asked Questions
How much do technical writers charge per hour?
Freelance technical writers charge $55–$150 per hour in the US. Entry-level writers (0–2 years) run $45–$70/hr, mid-level (3–6 years) $65–$100/hr, and senior writers (7+ years) $90–$150/hr. API and SDK documentation sits at the top of the range because it requires reading code and validating samples, while help-center and SOP work sits lower. SaaS engagements pay roughly 10–15% more than general technical writing thanks to fast release cycles and well-funded budgets.
What is a good rate for API documentation?
A good rate for API documentation is $65–$150/hr, $0.40–$1.20 per word, or $90–$280 per page for a mid-to-senior freelance technical writer. API docs command a premium over user manuals because the writer has to read source code, run the endpoints, and keep code samples accurate. For a defined deliverable — a full REST or GraphQL reference plus quickstart guides — many writers quote per project in the $3,000–$15,000 range depending on endpoint count and how much the engineering team has already documented.
Should technical writers charge per word, per page, or per hour?
Per hour is safest for evolving products and SME-dependent work where scope is unknown up front — common in early-stage SaaS. Per page (≈250 words) works well for manuals and structured docs with predictable length; define a page in the contract so screenshots and code blocks don't inflate the count. Per word fits clean knowledge-base articles but penalizes the concise writing good docs require. Per project is the most profitable once you can estimate a doc set reliably, because it rewards speed and tooling.
Do SaaS technical writers earn more than hardware technical writers?
Slightly. SaaS technical writing pays about 10–15% above general rates because release cycles are fast, documentation is continuous, and budgets are well funded by venture or recurring revenue. Hardware and embedded documentation pays a smaller premium (~8%) but is steadier and often regulated or safety-critical, which rewards writers who can handle compliance, firmware, and standards work. The deliverable mix matters more than the industry: an API reference pays more than a printed user manual in either sector.
Do technical writers earn more than copywriters?
Per hour, usually yes: technical writing runs $55–$150/hr against $50–$100/hr for general content copywriting. Per word it flips at the top, because conversion copywriters charge $0.20–$1.50 per word on sales pages where the client is buying attributable revenue rather than accuracy. Technical writing pays a narrower, steadier band and pays it regardless of how the last piece performed, while copywriting rates depend on portfolio results. Translation sits below both at $0.08–$0.32 per word and $35–$85/hr, because the source text fixes the word count and the premium comes from the scarcity of the language pair.