Template-based PDF generation
Create dynamic PDFs by filling Word templates with JSON data. Generate invoices, reports, and business documents, with full control over content and formatting. Support for PDF/UA accessibility standards. Perfect for automated document workflows.
By submitting this form, you agree to Nutrient’s Privacy Policy and Terms of Service.
Design PDF layouts in Microsoft Word and populate them with data programmatically. Non-technical users can modify templates without code changes.
Fill templates with JSON data structures. Support for complex data types, nested objects, loops, and conditional rendering logic.
Generate accessible PDF/UA-compliant documents from templates. Meet accessibility requirements and regulatory standards automatically.
Automate invoice generation, business reports, contracts, and data-driven documents, with high-volume batch processing and consistent formatting.
Create PDFs from DOCX templates with dynamic placeholder replacement.
Populate templates with structured JSON data from any source.
Create accessible documents that comply with PDF/UA standards.
Automate invoice creation with branded templates and customer data.
Generate business reports with charts, tables, and dynamic content.
Generate thousands of documents efficiently with parallel processing.
Convert documents to PDFs that meet industry standards for accessibility, archival, and regulatory compliance. Support for PDF/A and PDF/UA ensures your converted documents work everywhere.
PDF/A-1a PDF/A-1b PDF/A-2a PDF/A-2b PDF/UA Tagged PDFs Section 508 WCAG 2.0 DOCX DOC XLSX XLS PPTX PPT ADVANCED CAPABILITIES
Batch convert multiple documents, merge converted files, extract specific pages, apply watermarks, and automate complex document transformation workflows.
Process multiple documents in parallel with thread-safe APIs for high-volume conversion scenarios.
Convert specific pages, worksheets, or slides instead of entire documents for optimized output.
Automatic file format detection and conversion routing for handling unknown document types.
Headless conversion for automated workflows, scheduled jobs, and microservice architectures.
Nutrient Java SDK supports Java 8 and later, including Java 11, 17, and 21 LTS versions. You can deploy on any platform that runs the JVM, including Linux servers, Windows Server, macOS, Docker containers, Kubernetes clusters, AWS, Azure, Google Cloud, and on-premises infrastructure. The SDK works with Spring Framework, Spring Boot, Jakarta EE, and standalone Java applications.
No, absolutely not. The SDK includes built-in conversion engines that process Word, Excel, and PowerPoint files directly without requiring Microsoft Office installation. This eliminates Office licensing costs, simplifies server deployment, and enables conversion on any platform, including Linux and containerized environments where Office cannot be installed.
The SDK provides high-fidelity conversion that preserves fonts, formatting, layouts, tables, images, headers, footers, and page numbering. Complex elements like embedded objects, charts, and conditional formatting are maintained. For best results, use standard Office features and avoid proprietary extensions. Conversion accuracy is production-ready for most business documents, contracts, reports, and presentations.
Yes. The SDK supports bidirectional conversion. You can extract PDF content to Word documents with intelligent text reflow, convert tabular data from PDFs to Excel spreadsheets, and transform PDF pages into PowerPoint slides. The quality of reverse conversion depends on the source PDF structure. Tagged PDFs with proper semantic structure convert better than scanned or image-based PDFs.
The SDK is designed for high-volume server-side processing. Use
Java’s ExecutorService to process multiple documents
in parallel threads, configure memory allocation based on document
sizes, and implement streaming for very large files to avoid loading
entire documents into memory. The SDK is thread-safe and supports
concurrent conversion operations. For distributed processing, deploy
across multiple servers or containers.
Yes. The SDK supports generating PDF/UA (Universal Accessibility)-compliant documents that meet Section 508 and WCAG 2.0 requirements. During conversion, you can enable tagging to create semantic document structure, define reading order for screen readers, add alternative text for images, and set document metadata like language and title. The SDK provides APIs to validate accessibility compliance after conversion.
Conversion performance depends on document complexity, size, and conversion direction. Typical Office documents convert to PDF in seconds. For optimization, process documents asynchronously in background threads, cache conversion results when possible, convert only required pages or worksheets, and allocate sufficient JVM heap memory. The SDK includes no per-document licensing restrictions, so you can scale horizontally across multiple servers for high-volume scenarios.
The SDK uses standard Java exception handling patterns with detailed error messages. Every conversion method returns status indicators or throws specific exceptions for different failure scenarios like unsupported formats, corrupted files, or memory limits. Implement try-catch blocks around conversion operations, log errors with document context for debugging, validate input files before conversion, and use the SDK’s format detection to handle unknown file types gracefully.
The SDK uses a per-server licensing model based on the number of servers or containers running the SDK, not per document or per user. A single license allows unlimited document conversions on that server. Licensing covers development, staging, and production environments, with volume discounts for multi-server deployments. Start with a free trial that includes full functionality to evaluate the SDK in your environment.
Yes. The SDK is designed for containerized and cloud-native deployments. It runs in Docker containers on any orchestrator (Kubernetes, Docker Swarm, ECS), supports Linux-based containers for cost-effective cloud deployment, works on AWS Lambda with appropriate memory configuration, and runs on Azure Functions and Google Cloud Functions. The SDK has no UI dependencies and operates headless, making it ideal for microservice architectures and serverless computing.