Apryse Blog

For years, many Android scanning applications relied on portrait lock to provide a consistent and predictable user experience. As Android expands across tablets, foldables, Chromebooks, and desktop-style environments, Google is increasingly pushing developers toward adaptive layouts that work across different screen sizes and orientations.

Summary: DOCX Editor now includes a highlight markup tool, giving reviewers a way to flag text without opening a full comment thread. This release also speeds up search and replace on long documents.

Summary: Spreadsheet Editor now supports threaded comments and replies, using the same Notes Panel UI already live in WebViewer and DOCX Editor. Teams reviewing PDF, DOCX, and Excel files now get one consistent way to comment, reply, and collaborate across every format.

Retagging a PDF for PDF/UA compliance can pass automated validation while quietly wiping out the Alt text someone carefully wrote in Word. Acrobat, Xodo PDF Studio, and Nutrient all behave this way, because autoConvert rebuilds the tag tree from scratch. This article shows how to use the Apryse SDK to preserve that work. You’ll see why tag IDs and MCIDs can’t be used to link old and new tags, and how matching images by page location solves the problem.

The six-step Node.js approach extracts the existing Alt text, retags the document, matches old and new image tags by overlap, and copies the Alt text across. You’ll also see how unmatched items are logged for manual review.

Find out how to fix a PDF that has tags but still fails PDF/UA checks. Starting with a Word-exported document that PAC and veraPDF both flag, you’ll see how the Apryse SDK’s PDFUAConformance autoConvert call rebuilds tags, adds a missing title, and fills in image Alt text so the file passes validation. You’ll also learn why passing isn’t the end of the story: titles like “TRN-31616” and Alt text like “Image1” are technically present but not meaningful. The article shows three ways to review and improve them, using Xodo PDF Studio, the Apryse Server SDK (including LLM-generated descriptions), and a WebViewer-based review workflow that keeps a human in the loop.

A green checkmark from an accessibility checker doesn’t guarantee a PDF is truly PDF/UA compliant. You’ll learn what PDF/UA-1 and PDF/UA-2 require, including tagged structure, reading order, alt text, artifacts, metadata, and embedded fonts, and why PDF/UA-2 isn’t simply a superset of PDF/UA-1. Using two free tools, veraPDF and PAC, you’ll see how to validate a file through a UI or the command line, how to read the reports for compliant and non-compliant documents, and where each tool falls short, such as PAC’s lack of PDF 2.0 support. You’ll also see why automated checks must be paired with human review of reading order and artifacts.

The contract startup skipped building its own word processor by embedding Apryse DOCX Editor, allowing engineers to focus on contract workflows and the user experience.

Fall 2026 release brings pipeline-ready Markdown extraction, higher-level document generation, more consistent editing APIs, and more resilient document capture directly into Apryse SDKs

Apryse SDK Summer 2026 release introduces AI-powered OCR, intelligent document editing, and advanced capture capabilities that help developers transform complex documents into trusted, structured data for enterprise AI.

Law enforcement officers are guided by complex and specific local laws, regulations, and policies. But in the field, accessing and referencing this critical information is a challenge, historically relying on memory, phonebook-like manuals or calling for assistance.

Blue Voice tackles this challenge with its CJIS-compliant AI platform, providing law enforcement officers with immediate access to accurate legal, policy, and community resources, directly from the browser or smartphone.

When it’s time to add new capabilities to a software project, developers and leaders face the decision: build or buy? Juume AI faced this decision during development of the AI compliance platform CapraOne.

Sometimes the best way to grow is to ask the question you’re worried might sound “stupid.” Curiosity has played a big role in Lau’s journey, from learning the technology behind our products to growing from a Business Development Representative into an Account Executive. But what helped him along the way was his willingness to ask questions and his openness to learning. Lau realized early on that Apryse is a place where you don’t need to pretend to have all the answers. You just need to be willing to learn.

For Sofiia Khaikina, authenticity was not a nice-to-have; it was one of the most important things she was looking for in a workplace. From her first conversations, she saw a culture where people are encouraged to show up as they are and immediately felt she belonged. In this employee spotlight, she shares why that sense of belonging made Apryse stand out and how it continues to shape her experience today.

The right workplace is about more than just the role. It's about finding a team, culture, and environment where you can thrive. For Caio Nunes, Enterprise Account Manager, Apryse has been exactly that.

Summary: Enterprise-grade infrastructure isn't just for enterprises anymore. For years, growing teams have faced a false choice: start with lightweight, affordable tools that break down under real production demands, or lock into expensive enterprise contracts built for a company five times their size. This piece makes the case that "enterprise-grade" should be understood as a quality standard, not a pricing tier, breaking it down into five measurable traits (performance, security, reliability, scalability, and cost predictability) and showing why growing companies increasingly need that standard from day one, not after a costly rebuild forces the issue.

Summary: to implement document processing capabilities, developers consider a range of solutions, from open-source libraries, to Cloud API services, to commercial SDKs like Apryse. This article helps developers understand the advantages and disadvantages of each approach, including seven important cost dimensions to consider.

Summary: Scaling document generation in regulated industries requires getting three things right: template-based merging of structured data into finished documents, a governance layer that controls template versions and access, and a compliance foundation built on audit trails, data residency, and long-term archival standards. When these three are handled properly, adding a new document type is a simple template update rather than a full pipeline rebuild. This article covers batch processing patterns, client-side vs. server-side generation tradeoffs, template governance and audit considerations, and how these principles play out in real-world lending, insurance, healthcare, and legal workflows, plus a comparison of platforms for teams evaluating their options.