DocSpry.Pdf SDK · For developers

C# .NET PDF SDK.
For your next workflow.

Evaluate DocSpry.Pdf SDK for C# and .NET document applications, publishing platforms, and internal production tools. Contact our support team for SDK access, API documentation, supported modules, and licensing.

Contact our support team for SDK access

Start with the problem you’re solving

A PDF SDK for
your document workflow.

Bring us your integration requirements. These use cases help define what to test and which capabilities to discuss.

01 / DOCUMENT INTELLIGENCE

PDF text extraction for search and AI

A search or retrieval application needs useful context, not just a stream of text. Define how headings, paragraphs, tables, and page references should reach your index or retrieval pipeline.

Evaluate: reading order, page citations, table relationships, and the output structure your application consumes.

Why reading order matters
02 / PUBLISHING PLATFORMS

Document conversion in a publishing pipeline

Publishers often need several editions from one source. Map the handoff between document intake, editorial review, and delivery to an ebook platform or journal production system.

Evaluate: required EPUB or XML outputs, images, metadata, validation reports, and the modules available for each step.

Explore the journal XML workflow
03 / PRODUCTION SOFTWARE

PDF rendering and document review

A review tool needs a dependable connection between what the reviewer sees and what the document contains. Define your preview, page navigation, and source-reference requirements before choosing an integration.

Evaluate: representative page layouts, fonts, images, coordinate alignment, and the rendering environments your product requires.

04 / ACCESSIBLE PUBLISHING

Structure and quality checks in your workflow

Accessibility work combines document structure with editorial judgment. Map where headings, reading order, image descriptions, tables, and quality reports belong in your application.

Evaluate: available tagging and validation modules, human review checkpoints, and the deliverable requirements of your receiving system.

Plan your accessibility review

Choose your approach

PDF SDK or browser workflow?

Choose based on where the document work belongs: inside your own software, or in a ready-to-use publishing workspace.

DecisionDocSpry.Pdf SDKDocSpry web application
Who it servesDevelopers evaluating PDF capabilities for C# and .NET applications.Professionals and teams converting and reviewing documents in a browser.
Before you startConfirm APIs, modules, runtime compatibility, and deployment requirements with support.Try a born-digital PDF and review the EPUB, accessible PDF, NIMAS, or journal XML workflow.
Commercial accessRequest evaluation and production licensing terms for internal use, SaaS, or redistribution.Choose a monthly or annual fixed-term plan based on conversion capacity and user count.

Web application plans do not include an SDK license. Discuss SDK licensing or explore the professional and team workflow.

A useful evaluation starts small

Prove the fit.
Then build it in.

Choose a few documents that represent your real workload. Agree on the required outputs and acceptance checks before scaling an integration.

Discuss your evaluation
  1. 01

    Define the environment

    Share your programming language, .NET version where relevant, operating system, architecture, and intended hosting model. Confirm runtime and deployment support for the evaluation package.

  2. 02

    Choose representative files

    Include typical layouts and difficult cases: multiple columns, dense tables, embedded fonts, or complex figures. Specify whether your source is born-digital or scanned.

  3. 03

    Check the result your users need

    Compare content order, page references, output structure, and visual results against your acceptance criteria. Identify where a reviewer needs to intervene.

  4. 04

    Agree on the production scope

    Confirm the available APIs, expected workload, deployment rights, updates, and support. Keep the evaluation package version and test results with your integration notes.

Developer access & commercial licensing

Let’s talk about
what you’re building.

Contact our support team for DocSpry.Pdf SDK access and licensing. Tell us where PDF fits in your product so we can help with technical requirements and the terms for your intended use.

Sign in to send a saved enquiry to the support team.
Prefer to write directly? support@docspry.com

PDF SDK questions,
answered.

How do I get access to the DocSpry.Pdf SDK?

Contact the DocSpry support team at support@docspry.com for DocSpry.Pdf SDK access. Include your use case, language or runtime, deployment environment, and required PDF operations. Our team will help with access, API documentation, setup instructions, and licensing.

How do I get the SDK package and documentation?

Contact our support team for the DocSpry.Pdf SDK package, API documentation, and current distribution instructions. Confirm the available modules and evaluation terms with the team before integrating.

Can I use the SDK from C# and .NET?

The SDK development project targets C# and .NET. Include your required .NET version, operating system, and architecture in your request so we can confirm compatibility and the right evaluation build. Support for other languages or deployment environments should be confirmed with the team.

Which PDF operations and outputs can I use?

Start with the operations your application needs: text extraction, page rendering, document structure, or publishing outputs. The team will confirm the modules and APIs available for your evaluation. The hosted DocSpry application’s features should not be treated as an SDK feature list.

How is PDF SDK licensing priced?

Contact us with your product, deployment model, required modules, and expected volume for the applicable licensing terms. Discuss evaluation, production use, redistribution, updates, and support before committing. Hosted application plan prices are not an SDK quote.

Can I evaluate scanned PDFs or accessibility workflows?

Describe these requirements in your request. OCR, tagging, validation, and human review are different parts of a document workflow. Confirm the available SDK modules for each step and test representative files before selecting a production approach.

Do I need the SDK to convert a document?

For an interactive conversion and review workflow, use the DocSpry web application. SDK access is for developers evaluating integration into their own software. You can also explore our AI assistant connector for conversational document workflows.

Working on a document today?

Start in your browser.

For a ready-to-use conversion and editorial review workflow, explore the DocSpry web application.

Try DocSpry free