Choosing the right .NET document SDK is critical for teams automating document and PDF workflows. At Xceed, we offer two developer-first .NET document SDKs Words for .NET and PDF Library for .NET so you can ship reliable document features faster.
At Xceed, we offer two separate, purpose-built document SDKs:
- Words for .NET: a Word/document library for creating and manipulating documents programmatically.
- PDF Library for .NET: a dedicated PDF library for generating and working with PDF files in .NET.
Different formats, different workflows, same goal: help .NET developers ship reliable document features faster.
1) Words for .NET (document/Word workflows)
Words for .NET is designed for teams that want a code-first way to work with documents in .NET, Especially when you need to generate or update documents from application data.
Common use cases
- Document generation: invoices, contracts, letters, statements, reports
- Template-based assembly: start from a Word template and inject dynamic data
- Document updates: merge content, replace sections, update fields
- Back-office automation: scheduled jobs that generate documents in batches
What to look for in a Word/document library
- Template-friendly workflows (so non-dev stakeholders can own the layout)
- Maintainable API surface (readable code that doesn’t become a maze)
- Predictable output (consistent results across machines and build agents)
2) PDF Library for .NET (PDF workflows)
PDF Library for .NET is a dedicated PDF SDK for when PDF is the primary deliverable not just an export format.
Common use cases
- Generate PDFs directly for customer downloads, statements, receipts, and reports
- Server-side PDF creation in background workers and batch jobs
- Compliance and archiving workflows where PDF is the long-term record
- Customer-facing exports inside portals, dashboards, and admin tools
What to look for in a PDF library
- Production reliability (PDF generation becomes business-critical fast)
- Performance under load (PDF creation often runs in batches)
- A developer-first API (so your team can implement features without fighting the library)
How to choose between them
Use this quick rule of thumb:
- Choose Words for .NET when your workflow starts with documents/Word templates and you need document assembly or document editing.
- Choose PDF Library for .NET when your workflow starts and ends with PDF, generation, manipulation, compliance, and distribution.
If you have both requirements (common in real apps), you can evaluate each product independently and adopt what fits your architecture.
Get a 45-day trial (immediate download)
If you want to validate either library in your own codebase, start with a 45-day trial.
- Trial page: https://xceed.com/trial/
- Support (weekdays, 9–5 EST): https://xceed.com/support/
Quick evaluation checklist (use for either product)
- Pick one “must-work” output (invoice, statement, report)
- Build a minimal end-to-end flow (data → document/PDF → file)
- Validate output consistency (dev machine + CI/build server)
- Load test with realistic batch sizes
Bundle both: get Words + PDF in one offer
If you need both Word/document workflows and PDF workflows, you don’t have to piece together multiple tools.
Bundle Words for .NET + PDF Library for .NET and get both in one product for $100.
- Start here: https://xceed.com/trial/
FAQ
Are Words for .NET and PDF Library for .NET the same product?
No, they’re two separate products. Words for .NET focuses on document/Word workflows, while PDF Library for .NET is a dedicated PDF SDK.
Can I trial them without talking to sales?
Yes. The trial is immediate download after completing the form.
How long is the trial?
45 days.
Where do I go if I hit an issue during evaluation?
Use the support page here: https://xceed.com/support/