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 |
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).
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 for technical writers
Books and gear that show up on working technical writers' desks. Affiliate links — buying through them helps fund this calculator.
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.
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 or topic-based docs.
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.
As an Amazon Associate this site earns from qualifying purchases. Links are sponsored.
Related Calculators & Guides
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.