<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Syncfusion, Inc. - Medium]]></title>
        <description><![CDATA[Syncfusion provides third-party UI components for React, Vue, Angular, JavaScript, Blazor, .NET MAUI, ASP.NET MVC, ASP.NET Core, WinForms, WPF, UWP, Flutter, and WinUI. - Medium]]></description>
        <link>https://medium.com/syncfusion?source=rss----f6ee85f5a2---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Syncfusion, Inc. - Medium</title>
            <link>https://medium.com/syncfusion?source=rss----f6ee85f5a2---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:07:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/syncfusion" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Automate Digital Signatures in Word Documents Using C#]]></title>
            <link>https://medium.com/syncfusion/how-to-automate-digital-signatures-in-word-documents-using-c-33e7b07d172d?source=rss----f6ee85f5a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/33e7b07d172d</guid>
            <category><![CDATA[dotnet-word-library]]></category>
            <category><![CDATA[digital-signatures]]></category>
            <category><![CDATA[whats-new]]></category>
            <category><![CDATA[file-format]]></category>
            <category><![CDATA[csharp]]></category>
            <dc:creator><![CDATA[Rajeshwari Pandinagarajan]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 11:50:04 GMT</pubDate>
            <atom:updated>2026-11-16T11:50:03.839Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="How to Automate Digital Signatures in Word Documents Using C#" src="https://cdn-images-1.medium.com/max/1024/0*AlEDhMXSazfRZbQq.jpg" /></figure><blockquote><strong>TL;DR:</strong> Still signing Word documents manually? With the Syncfusion .NET Word Library, you can automate the entire signing process using C#. Learn how to add invisible digital signatures, create visible signature lines, validate signed documents, and manage document revisions without Microsoft Word or Office Interop.</blockquote><p>Have you automated Word document generation but still need someone to sign each document manually? This extra step can slow down approvals, create multiple document versions, and make it harder to track signed files.</p><p>What if you could handle the entire process directly in your application?</p><p>The Syncfusion® <a href="https://www.syncfusion.com/document-sdk/net-word-library">.NET Word Library</a> introduces <a href="https://www.syncfusion.com/document-sdk/net-word-library/digital-signature-in-word-document">digital signature</a> support in Essential Studio <a href="https://help.syncfusion.com/common/essential-studio/release-notes/v35.1.37">2026 Volume 3</a>. You can now sign, validate, and manage digital signatures in Word documents using C#, without depending on Microsoft Word or Office Interop.</p><p>With digital signatures built into your document process, you can handle document generation, signing, validation, and delivery in one automated process.</p><p>In this blog, you’ll learn how to:</p><ul><li>Add invisible digital signatures to Word documents.</li><li>Create and sign visible signature lines.</li><li>Validate signed DOCX files.</li><li>Remove signatures before making document changes.</li><li>Apply supported XML digital signature standards.</li><li>Manage multiple signature lines in a document.</li></ul><h3>Why automate digital signatures in Word documents?</h3><p>Signing a few documents manually may not be a problem. But what happens when your application generates hundreds of offer letters, contracts, or approval documents every day? Managing all those signatures manually can quickly become difficult.</p><p>Automating digital signatures helps applications:</p><ul><li>Reduce manual approval steps.</li><li>Avoid unnecessary document copies.</li><li>Maintain document integrity.</li><li>Validate signatures before sharing documents.</li><li>Improve document tracking and auditability.</li><li>Simplify approval processes.</li></ul><p>Consider an HR application that automatically generates offer letters. Without automation, HR teams need to download each document, sign it, upload the signed copy, and keep track of different versions.</p><p>With digital signature automation, the application can sign documents, validate them, and store the approved versions directly within the approval process.</p><p>Here’s how the manual and automated approaches compare:</p><figure><img alt="Manual vs. Automated Digital Signatures in Word Documents" src="https://cdn-images-1.medium.com/max/863/1*JpHmktBiO_kbmVd513aZFw.png" /></figure><h3>How to automate digital signatures in Word documents using C#</h3><p>Let’s see how to add <a href="https://help.syncfusion.com/document-processing/word/word-library/net/working-with-digital-signature">digital signatures</a> to Word documents using the Syncfusion <a href="https://help.syncfusion.com/document-processing/word/word-library/net/getting-started">.NET Word Library (DocIO)</a>.</p><p>We’ll walk through loading a document and signing certificate, creating invisible and visible signatures, validating signed documents, and managing document revisions.</p><p><strong>Note</strong>: The examples in this blog focus on DOCX documents. Digital signature support in DocIO is currently available for DOCX files, not legacy DOC formats.</p><h3>Step 1: Install the required NuGet package</h3><p>First, install the <a href="https://www.nuget.org/packages/Syncfusion.DocIO.Net.Core">Syncfusion.DocIO.Net.Core</a> NuGet package in your .NET application.</p><p>Run the following command in the <strong>Package Manager Console</strong>:</p><pre>Install-Package Syncfusion.DocIO.Net.Core</pre><p>Next, import the required namespaces:</p><pre>using Syncfusion.DocIO;<br>using Syncfusion.DocIO.DLS;<br>using Syncfusion.Office;<br>using System;<br>using System.IO;</pre><p>These namespaces provide the classes required to load Word documents, configure digital signatures, work with certificates, and save signed files.</p><h3>Step 2: Load the document and signing certificate</h3><p>Before adding a digital signature, you need two things:</p><ol><li>The Word document you want to sign.</li><li>A digital certificate containing the signer’s private key.</li></ol><p>The certificate is typically provided as a password-protected <strong>.pfx</strong> or <strong>.p12</strong> file.</p><p>You can load the DOCX document using the <strong>WordDocument</strong> class and the signing certificate using <strong>OfficeDigitalSignatureCertificate</strong>.</p><pre>using WordDocument document = new WordDocument(<br>    &quot;input.docx&quot;, FormatType.Docx);<br><br>OfficeDigitalSignatureCertificate certificate =<br>    new OfficeDigitalSignatureCertificate(<br>        &quot;PrivateKey.pfx&quot;, &quot;certificate-password&quot;);</pre><p><strong>Production tip</strong>: Avoid hardcoding certificate passwords in your application. Store certificates and secrets securely using solutions such as Azure Key Vault, enterprise secret management systems, or secure certificate stores.</p><p>Also, make sure the certificate is valid, contains the required private key, and has not expired.</p><h3>Step 3: Add an invisible digital signature to a Word document</h3><p>Not every document needs a visible signature block. Sometimes, you simply want to confirm who signed the document and whether its content has changed since signing.</p><p>That’s where <a href="https://help.syncfusion.com/document-processing/word/word-library/net/working-with-digital-signature#add-digital-signature-invisible-signature">invisible digital signatures</a> help. They protect the document without adding a visible signature area to the page.</p><p>With DocIO, you can use the <strong>AddDigitalSignature()</strong> method to sign a Word document using the loaded certificate.</p><p>You can configure the <strong>SignatureSettings</strong> class to specify details such as the signing time and comments.</p><pre>SignatureSettings settings = new SignatureSettings<br>{<br>    SignTime = DateTime.Now,<br>    Comments = &quot;Approved&quot;<br>};<br><br>document.AddDigitalSignature(certificate, settings);<br>document.Save(&quot;DigitallySigned.docx&quot;, FormatType.Docx);</pre><p>Here, <strong>SignTime</strong> specifies the signing time, while <strong>Comments</strong> stores additional information associated with the signature.</p><p>Once the signature is added, save the document in DOCX format.</p><p>The resulting document contains an invisible digital signature that can be validated later.</p><p><strong>Important</strong>: Avoid modifying a signed document. Changes to its content can invalidate the existing digital signature.</p><figure><img alt="Adding an invisible digital signature to a Word document" src="https://cdn-images-1.medium.com/max/938/0*ake7wIV5erpUKk7X.png" /><figcaption>Adding an invisible digital signature to a Word document</figcaption></figure><h3>Step 4: Add a visible digital signature to a Word document</h3><p>Some business documents need a visible approval area so readers can easily identify where a document was signed.</p><p>You may see these signature lines in:</p><ul><li>Contracts and legal agreements.</li><li>Employees offer letters.</li><li>Procurement approvals.</li><li>Financial authorization documents.</li><li>Business agreements.</li></ul><p>DocIO allows you to create a <a href="https://help.syncfusion.com/document-processing/word/word-library/net/working-with-digital-signature#sign-signature-line-visible-signature">signature line</a> with signer details and a unique identifier. You can then use this identifier when applying the digital signature through <a href="https://help.syncfusion.com/cr/document-processing/Syncfusion.Office.SignatureSettings.html">SignatureSettings</a>.</p><p>First, create a signature line in the Word document and retrieve its unique ID. The <strong>signatureLineId</strong> in the following example represents that ID.</p><p>You can also provide a signature image to give the signature line a familiar handwritten-signature appearance.</p><pre>byte[] SignatureLineImage = File.ReadAllBytes(&quot;signature.png&quot;);<br><br>SignatureSettings visibleSettings = new SignatureSettings<br>{<br>    SignatureLineId = signatureLineId,<br>    SignatureLineImage = SignatureLineImage,<br>    SignTime = DateTime.Now,<br>    Comments = &quot;Reviewed and approved&quot;<br>};<br><br>document.AddDigitalSignature(certificate, visibleSettings);<br><br>document.Save(<br>    &quot;VisibleDigitalSignature.docx&quot;, FormatType.Docx);</pre><p>Here:</p><ul><li><strong>SignatureLineId</strong> identifies the signature line to be signed.</li><li><strong>SignatureLineImage</strong> specifies the image displayed in the signature area.</li><li><strong>SignTime</strong> records the signing time.</li><li><strong>Comments</strong> adds information associated with the signature.</li></ul><p>The <strong>signatureLineId</strong> must match the unique ID of a signature line already created in the document.</p><p><strong>A quick clarification</strong>: The signature image provides the visual appearance of a handwritten signature. The certificate-based digital signature provides cryptographic verification and document integrity protection. Adding an image alone does not create a digital signature.</p><figure><img alt="Adding a visible digital signature to a Word document" src="https://cdn-images-1.medium.com/max/938/0*HesGUgGqGjmb_3Dq.png" /><figcaption>Adding a visible digital signature to a Word document</figcaption></figure><h3>Step 5: Validate digital signatures before sharing documents</h3><p>Adding a digital signature is only one part of the process. You should also check whether the signature is still valid before sharing, distributing, or archiving the document.</p><p>For example, an enterprise document management system can validate a signed DOCX file before moving it into permanent storage.</p><p>DocIO provides the <strong>DigitalSignatures</strong> collection to access the signatures in a Word document.</p><p>You can check whether a document contains signatures and whether those signatures are valid using the following properties:</p><ul><li><strong>DigitalSignatures.Count</strong>: Gets the number of signatures in the document.</li><li><strong>DigitalSignatures.IsValid</strong>: Checks whether all signatures in the collection are valid.</li><li><strong>signature.IsValid</strong>: Checks an individual signature.</li></ul><p>You can also retrieve details such as signing time and signature comments.</p><p>Here’s how to check the signatures in a document:</p><pre>using WordDocument signedDocument = new WordDocument(<br>    &quot;DigitallySigned.docx&quot;, FormatType.Docx);<br><br>bool hasSignatures = signedDocument.DigitalSignatures.Count &gt; 0;<br><br>bool allSignaturesValid =<br>    signedDocument.DigitalSignatures.IsValid;<br><br>foreach (var signature in signedDocument.DigitalSignatures)<br>{<br>    bool isValid = signature.IsValid;<br>    string comments = signature.Comments;<br>    DateTime signingTime = signature.SigningTime;<br>}</pre><p>This example checks whether the document contains signatures and whether they are valid. It also retrieves the validation status, comments, and signing time of each signature.</p><p>For example, before sending an approved contract to a customer, your application can validate its signatures and proceed based on the validation result.</p><figure><img alt="Validating a digital signature in a Word document" src="https://cdn-images-1.medium.com/max/938/0*F5u00JsffWI7qGoW.png" /><figcaption>Validating a digital signature in a Word document</figcaption></figure><p>Try the <a href="https://document.syncfusion.com/demos/word/digitalsignaturevalidation#/tailwind3">validation demo</a> to verify signed documents and explore additional validation scenarios.</p><h3>Step 6: Choose the right digital signature standard</h3><p>Different applications may have different digital signature requirements. Some may need standard XML digital signatures, while others may require additional signature policy information.</p><p>DocIO allows you to specify the required signature standard using the <a href="https://help.syncfusion.com/cr/document-processing/Syncfusion.Office.XmlDsigLevel.html">XmlDsigLevel</a> property in <strong>SignatureSettings</strong>.</p><p>It supports the following standards:</p><h4>XmlDSig</h4><p>XML Digital Signature (XMLDSig) is the standard W3C format for digitally signing XML content. It is suitable for standard document-signing scenarios.</p><h4>XAdES-EPES</h4><p>XAdES-EPES extends XML digital signatures with explicit signature policy information. This allows applications to associate a signature with a defined signing policy.</p><h4>Things to consider when choosing a standard:</h4><ul><li>Check your organization’s digital signature requirements.</li><li>Select a standard that aligns with the applicable signing policy.</li><li>Make sure the systems that receive and validate your documents support the selected standard.</li><li>Verify any additional compliance requirements separately.</li></ul><p>You can configure the required standard using the <strong>XmlDsigLevel</strong> enumeration. Here’s an example of configuring both standards:</p><pre>SignatureSettings xmlSettings = new SignatureSettings<br>{<br>    XmlDsigLevel = XmlDsigLevel.XmlDSig,<br>    SignTime = DateTime.Now<br>};<br><br>document.AddDigitalSignature(certificate, xmlSettings);<br><br>SignatureSettings xadesSettings = new SignatureSettings<br>{<br>    XmlDsigLevel = XmlDsigLevel.XAdEsEpes,<br>    SignTime = DateTime.Now<br>};<br><br>document.AddDigitalSignature(certificate, xadesSettings);</pre><p>Choose the appropriate standard based on your application’s requirements. Selecting a signature standard alone does not guarantee regulatory compliance; your complete signing process must meet the applicable certificate and policy requirements.</p><h3>Step 7: Remove digital signatures before updating a document</h3><p>Need to update a document after it has been signed? You should remove the existing signatures before making changes. Otherwise, the signatures may no longer be valid.</p><p>Consider a contract amendment. Once a contract has been signed, the business may need to update a clause or change an agreement date. The previous signature no longer represents the updated document.</p><p>With DocIO, you can use the <strong>RemoveAllDigitalSignatures()</strong> method to remove all digital signatures from a document.</p><p>Here’s how to do it:</p><pre>using WordDocument signedDocument = new WordDocument(<br>    &quot;DigitallySigned.docx&quot;, FormatType.Docx);<br><br>signedDocument.RemoveAllDigitalSignatures();<br><br>signedDocument.Save(<br>    &quot;UnsignedForRevision.docx&quot;, FormatType.Docx);</pre><p>A good approach is to follow these steps:</p><ol><li>Preserve the original signed document.</li><li>Create a separate working copy.</li><li>Remove signatures from the working copy.</li><li>Make the required document changes.</li><li>Apply new digital signatures after the changes are complete.</li></ol><p>Keeping separate signed and unsigned copies helps maintain a clear document history and makes it easier to track revisions.</p><figure><img alt="Removing a digital signature from a Word document" src="https://cdn-images-1.medium.com/max/938/0*BvduiELzCnp2Pwcp.png" /><figcaption>Removing a digital signature from a Word document</figcaption></figure><p>Learn more about <a href="https://help.syncfusion.com/document-processing/word/word-library/net/working-with-digital-signature#remove-digital-signature">removing signatures</a> before revising document content.</p><h3>Step 8: Manage multiple signature lines in a document</h3><p>What if a document needs approval from more than one person?</p><p>For example, a procurement agreement may need signatures from a department manager, finance manager, and authorized approver.</p><p>DocIO allows you to insert multiple signature lines into a Word document and sign each line individually.</p><p>You can create separate signature lines using the <strong>AppendSignatureLine()</strong> method. Each line has its own unique identifier, which you can retrieve and associate with the corresponding signer.</p><p>When signing, pass the appropriate identifier through the <strong>SignatureSettings.SignatureLineId</strong> property.</p><p>You can then apply the digital signature to each signature line and save the signed document.</p><p>This is useful for applications that need multiple approval sections in the same document.</p><p><strong>Note</strong>: DocIO provides the document-level signature capabilities. Your application is responsible for managing the approval process, such as assigning signers, sending notifications, controlling signing order, and tracking approval status.</p><h3>Common scenarios for digital signature automation</h3><p>Digital signature automation can be useful in several types of applications.</p><p>Here are a few examples:</p><ul><li><strong>HR applications</strong>: Automatically sign employees offer letters, appointment letters, and other employment documents.</li><li><strong>Contract management systems</strong>: Sign agreements and validate them before sharing with customers or partners.</li><li><strong>Procurement applications</strong>: Manage purchase agreements and approval documents.</li><li><strong>Financial applications</strong>: Sign financial reports and authorization documents.</li><li><strong>Document management systems</strong>: Validate signed documents before storing or archiving them.</li></ul><p>In each scenario, automating digital signatures helps reduce manual work while keeping document signing and validation within the application.</p><h3>Frequently Asked Questions</h3><ol><li><strong>What is the difference between an invisible digital signature and a visible signature line?<br></strong>An invisible digital signature protects a document without displaying a signature area on the page.<br>A visible signature line provides a designated area for signing. It can display signer information and an optional signature image. The signature line must also be digitally signed using a certificate to provide cryptographic verification.</li><li><strong>Can multiple people sign the same DOCX document?<br></strong>Yes. DocIO supports multiple signature lines in a Word document. Each signature line has its own unique identifier and can be signed individually.<br>However, managing the approval sequence and signer interactions must be handled by your application.</li><li><strong>When should digital signatures be removed?<br></strong>Remove existing signatures whenever you need to modify the signed document. After making the required changes, apply new digital signatures to the updated document.<br>It’s good practice to preserve the original signed copy for document history and audit purposes.</li><li><strong>Which Word document formats support digital signatures in DocIO?<br></strong>DocIO currently supports digital signatures in DOCX format. Legacy DOC documents are not supported for this feature.</li><li><strong>Which digital signature standards are supported in the .NET Word Library?<br></strong>DocIO supports <strong>XMLDSig</strong> and <strong>XAdES-EPES</strong> through the <strong>SignatureSettings.XmlDsigLevel</strong> property. You can select the appropriate standard based on your application’s signing requirements.</li><li><strong>Can I use a signature image without a digital certificate?<br></strong>A signature image provides a visual representation of a handwritten signature. However, an image alone does not provide cryptographic verification or protect the document from undetected changes.<br>To create a digital signature, you need a valid signing certificate containing a private key.</li></ol><h3>Keep document signing within your application</h3><p>Why handle document signing manually when you can automate it directly in your .NET application?</p><p>With the Syncfusion <a href="https://www.syncfusion.com/document-sdk/net-word-library">.NET Word Library</a>, you can add invisible digital signatures, create visible signature lines, validate signed documents, and manage document revisions using C#.</p><p>Whether you’re building an HR application, contract management system, or enterprise document process, these capabilities help reduce manual steps while maintaining document integrity and auditability.</p><p>Ready to try it in your application? Explore the <a href="https://help.syncfusion.com/document-processing/word/word-library/net/working-with-digital-signature">digital signature documentation</a> and download the <a href="https://github.com/SyncfusionExamples/DocIO-Examples/tree/main/Digital-Signature">GitHub samples</a> to see the complete implementation.</p><p>This feature is available in the Essential Studio <a href="https://www.syncfusion.com/forums/198591/essential-studio-2026-volume-3-main-release-v35-1-37-is-available-for-download">2026 Volume 3</a> release. You can also explore the <a href="https://www.syncfusion.com/products/release-history">Release Notes</a> and <a href="https://www.syncfusion.com/products/whatsnew">What’s New pages</a> for additional updates.</p><p>Existing customers can access the latest version through the <a href="https://www.syncfusion.com/sales/pricing?category=ui-components">License and Downloads</a> page. New users can start a <a href="https://www.syncfusion.com/downloads">30-day free trial</a> and explore the capabilities of the Syncfusion .NET Word Library.</p><p>If you have questions or feedback, reach out through our <a href="https://www.syncfusion.com/forums">support forums</a>, <a href="https://support.syncfusion.com/">support portal</a>, or <a href="https://www.syncfusion.com/feedback">feedback portal</a>. We’re happy to help!</p><h3>Related Blogs</h3><ul><li><a href="https://www.syncfusion.com/blogs/post/syncfusion-essential-studio-2026-vol-3">What’s New in Syncfusion Essential Studio 2026 Volume 3: A2UI, New JavaScript Document Libraries, and More</a></li><li><a href="https://www.syncfusion.com/blogs/post/document-processing-2026-volume-3-update">Syncfusion Document SDKs 2026 Volume 3: New JavaScript Libraries and Faster Excel Processing</a></li><li><a href="https://www.syncfusion.com/blogs/post/document-sdks-2026-volume-3">What’s New in Syncfusion Document SDKs 2026 Volume 3: AI Chunking, PDF Security, and Data Extraction</a></li><li><a href="https://www.syncfusion.com/blogs/post/whats-new-2026-vol-3-document-solutions">Struggling with Complex Document Tasks? Explore Syncfusion Essential Studio 2026 Volume 3</a></li></ul><p><em>Originally published at </em><a href="https://www.syncfusion.com/blogs/post/automate-digital-signature-word-csharp"><em>https://www.syncfusion.com</em></a><em> on November 13, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33e7b07d172d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/syncfusion/how-to-automate-digital-signatures-in-word-documents-using-c-33e7b07d172d">How to Automate Digital Signatures in Word Documents Using C#</a> was originally published in <a href="https://medium.com/syncfusion">Syncfusion, Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Who’s Who and a What’s What of GDPR]]></title>
            <link>https://medium.com/syncfusion/a-whos-who-and-a-what-s-what-of-gdpr-0047eef3ce0c?source=rss----f6ee85f5a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/0047eef3ce0c</guid>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[data-privacy]]></category>
            <category><![CDATA[gdpr]]></category>
            <dc:creator><![CDATA[Rajeshwari Pandinagarajan]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 13:57:01 GMT</pubDate>
            <atom:updated>2026-11-13T13:57:01.276Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A Who’s Who and a What’s What of GDPR" src="https://cdn-images-1.medium.com/max/938/0*11JymaKXKRn6TNFU.png" /></figure><blockquote><strong>TL;DR:</strong> GDPR affects any organization that collects or processes personal data from individuals in the EU. This article introduces the key GDPR concepts, including personal data, anonymized data, and special category data, while explaining the roles of data controllers, processors, data subjects, DPOs, and GDPR representatives. It provides a practical foundation for understanding how modern data protection regulations work and why compliance matters.</blockquote><p>The General Data Protection Regulation (GDPR) is the European Union’s comprehensive law that sets strict rules for how organizations collect, use, and protect EU citizens’ personal data, regardless of where the organization is based. It establishes individual rights, mandates accountability, and turns data privacy from a best practice into a legal obligation with global reach.</p><p>“Who’s Who and a What’s What of GDPR” refers to understanding who the key roles are in the General Data Protection Regulation, such as data subjects, controllers, and processors, and what the important GDPR concepts are, like personal data, anonymized data, and more.</p><h3>What’s What: Key Concepts</h3><h3>Personal Data</h3><p>Personal data is any information that relates to an individual who can be directly or indirectly identified. Names, email addresses, credit card numbers, date of birth, etcetera are probably the first that come to mind when you think of the definition of personal data. However, location information, such as IP address, or other online identifiers, such as cookie ID, can also be personal data.</p><h3>Anonymized Data</h3><p>Anonymized data is personal data that, through the use of technology, has been rendered anonymous so that it is no longer possible to identify an individual through the data, either directly or indirectly, or in combination with other data.</p><p>Anonymized data is not personal data and is therefore not covered by the GDPR -provided that the personal data has been anonymized in accordance with the three criteria laid down by the European Data Protection Authorities.</p><h3>Special Category Data</h3><p>GDPR classifies the following types of personal data as potentially more sensitive and provides them with additional protection:</p><p>The special categories of personal data are:</p><ul><li>Personal data about racial or ethnic origin.</li><li>Personal data about political opinions.</li><li>Personal data about religious or philosophical beliefs.</li><li>Personal data about trade union membership.</li><li>Genetic data.</li><li>Biometric data (where used for identification purposes)-this could be data such as fingerprints or retina scans.</li><li>Data concerning health.</li></ul><p>These types of personal data merit specific protection and must be handled with greater care, as using them could create significant risks to an individual’s fundamental rights and freedoms or expose them to discrimination.</p><h3>Who’s Who: Key Roles</h3><h3>Data Controller</h3><p>The data controller determines the purposes for which and how personal data is processed. So, if your company or organization decides why and how the personal data should be processed, it is the data controller. Employees process personal data within your organization to fulfill their tasks as data controllers.</p><h3>Data Processor</h3><p>A data processor is the individual (other than an employee of the controller) or the legal person that carries out processing activities, on behalf of and in accordance with the controller’s instructions. In other words, the data controller can provide personal data to the data processor to carry out such processing activities on its behalf. A legal agreement governs arrangements between the data controller and the data processor.</p><h3>Data Subject</h3><p>A data subject is any individual whose personal data is being collected, processed, or stored. This could include names, email addresses, ID numbers, IP addresses, biometric data, and anything else covered under GDPR’s definition of personal data. Under regulations like GDPR, the data subject is the individual the data refers to and is central to modern data protection laws.</p><h3>Data Protection Officer</h3><p>Some data controllers must have a Data Protection Officer (DPO), while others choose to appoint a DPO (or an assigned individual) to handle data protection matters on their behalf. Individuals can also contact the DPO with data protection queries or concerns. If a company has no DPO, other people in the company will address any data protection queries or concerns on behalf of the data controller. Note that these individuals are not data controllers themselves; they are acting on behalf of the data controller.</p><h3>GDPR Representative</h3><p>If you do not have an office in the EU/EEA but still process data from individuals based in the EU/EEA, then you still need to comply with the GDPR regarding your data processing, and the GDPR requires you to appoint a representative. This representative must be based in an EU or EEA state where some of the individuals whose personal data you process are located.</p><p>You must authorize the representative in writing to act on your behalf for GDPR compliance. Be aware that a Data Representative is not a Data Protection Officer (DPO). It has a distinct role with its own responsibilities. The representative’s role is to ensure that you comply with the GDPR by enabling communication with individuals in Europe and European data protection authorities.</p><p>You should provide details of your representative to EEA-based individuals whose personal data you process, typically by including the contact details in your privacy policy. The representative must also be able to act on your behalf with European data protection authorities.</p><h3>Conclusion</h3><p>As we’ve explored, GDPR is more than just a set of rules; it’s a fundamental shift in how we approach data protection. It empowers individuals, holds organizations accountable, and aims to create a safer digital environment for all of us. Whether you’re an individual concerned about your privacy or a business striving for compliance, understanding GDPR is crucial in today’s data-driven world.</p><p>GDPR compliance is an ongoing journey. It requires continuous attention, adaptation, and improvement. But by embracing its principles and implementing robust data protection practices, we can all contribute to a digital landscape where personal data is respected and protected.</p><p><em>Originally published at </em><a href="https://www.syncfusion.com/blogs/post/gdpr-roles-and-responsibilities"><em>https://www.syncfusion.com</em></a><em> on November 12, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0047eef3ce0c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/syncfusion/a-whos-who-and-a-what-s-what-of-gdpr-0047eef3ce0c">A Who’s Who and a What’s What of GDPR</a> was originally published in <a href="https://medium.com/syncfusion">Syncfusion, Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing BoldDocServer: An Office Online Server Alternative for SharePoint Server]]></title>
            <link>https://medium.com/syncfusion/introducing-bolddocserver-an-office-online-server-alternative-for-sharepoint-server-461d6a083ed8?source=rss----f6ee85f5a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/461d6a083ed8</guid>
            <category><![CDATA[document-editor]]></category>
            <category><![CDATA[pdf-viewer]]></category>
            <category><![CDATA[spreadsheet-editor]]></category>
            <category><![CDATA[bolddocserver]]></category>
            <category><![CDATA[document-collaboration]]></category>
            <dc:creator><![CDATA[Rajeshwari Pandinagarajan]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 13:49:33 GMT</pubDate>
            <atom:updated>2026-11-13T13:49:33.066Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Introducing BoldDocServer: An Office Online Server Alternative for SharePoint Server" src="https://cdn-images-1.medium.com/max/1024/1*RHdUnZuNT7xWZhsJZFm6HA.jpeg" /></figure><blockquote><strong>TL;DR:</strong> <strong>Syncfusion introduces BoldDocServer</strong>, a new solution for browser-based Word, Excel, and PDF experiences in SharePoint Server. With Office Online Server support ending on <strong>December 31, 2026</strong>, BoldDocServer gives organizations a new option to continue supported document viewing, editing, review, and collaboration while keeping SharePoint as the document repository.</blockquote><h3>Why BoldDocServer, and why now?</h3><p>December 31, 2026, is becoming an important date for organizations running Office Online Server with SharePoint Server.</p><p>Microsoft support for Office Online Server ends on that date. For teams that depend on browser-based document viewing and editing, the approaching deadline raises a practical question:</p><p><strong>What happens to those SharePoint document processes next?</strong></p><p>Some organizations may choose to change their broader Microsoft architecture. Others may want to continue operating SharePoint Server and replace the browser-based document layer that Office Online Server provided.</p><p>That second scenario is where <a href="https://www.bolddocserver.com/">BoldDocServer</a> fits.</p><p>Syncfusion® is introducing BoldDocServer to bring browser-based Word, Excel, and PDF experiences to SharePoint Server through WOPI. Users can work with supported documents from the browser, while SharePoint remains responsible for document storage, permissions, and repository operations.</p><p>Let’s look at what BoldDocServer provides, how it works with SharePoint, and what organizations evaluating their post-Office Online Server strategy should know.</p><h3>Office Online Server support ends December 31, 2026</h3><p>Office Online Server has long provided browser-based viewing and editing experiences for Microsoft Office documents in supported server environments.</p><p>According to <a href="https://learn.microsoft.com/en-us/lifecycle/products/office-online-server">Microsoft’s product lifecycle</a>, Office Online Server reaches the end of support on <strong>December 31, 2026</strong>.</p><p>That does not mean every existing deployment suddenly stops functioning on January 1, 2027. It does mean organizations relying on Office Online Server need a plan for operating beyond its supported lifecycle.</p><p>For organizations using SharePoint Server, now is the time to consider questions such as:</p><ul><li>Do we intend to continue running SharePoint Server?</li><li>Which browser-based document experiences do our users depend on?</li><li>Do we need Word and Excel editing directly from SharePoint?</li><li>Do users also need PDF viewing and review scenarios?</li><li>Which document permissions and repository processes must remain in SharePoint?</li><li>What replacement or migration path should we validate before the deadline?</li></ul><p>Planning early gives teams time to test document behavior, permissions, save-back processes, collaboration, and deployment requirements before Office Online Server reaches retirement.</p><h3>What are the options for SharePoint Server teams?</h3><p>There is no single path that fits every organization. Teams evaluating Office Online Server retirement may broadly consider the following approaches:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/893/1*AH21CptC1oh9eL_brwIhNQ.png" /></figure><p><strong>BoldDocServer is designed for the first path</strong>: Organizations that plan to continue using SharePoint Server while replacing the browser-based document experience provided by Office Online Server.</p><h3>Introducing BoldDocServer</h3><p><a href="https://www.bolddocserver.com/">BoldDocServer</a> is a Syncfusion product for browser-based document viewing, editing, review, and collaboration with SharePoint Server. It connects SharePoint with Syncfusion’s document experiences through the Web Application Open Platform Interface (WOPI).</p><p>The responsibilities remain clearly separated:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/1*g01KvBcxEjA2YYtaHzDy7A.png" /></figure><p>The important point is that BoldDocServer does not replace SharePoint as the document repository. SharePoint continues to store documents and manage access. BoldDocServer provides the browser-based experience for supported document types.</p><h3>Work with Word, Excel, and PDF documents from SharePoint</h3><p>BoldDocServer brings common enterprise document scenarios into the browser.</p><h3>Edit Word documents</h3><p>Users can open supported Word files stored in SharePoint through the integrated <a href="https://www.syncfusion.com/docx-editor-sdk">Syncfusion document editing experience</a>. They can view and modify supported document content and save supported changes back to SharePoint through the configured WOPI workflow.</p><p>Spell-check functionality can also be used when the required dictionary resources are configured.</p><h3>Work with Excel workbooks</h3><p>For Excel files, the integrated <a href="https://www.syncfusion.com/spreadsheet-editor-sdk">Syncfusion Spreadsheet Editor</a> provides the browser-based workbook experience.</p><p>Users can open workbooks stored in SharePoint, work with supported spreadsheet content, and save supported changes through the configured integration.</p><h3>Review PDF documents</h3><p>PDF document experiences use the integrated <a href="https://www.syncfusion.com/pdf-viewer-sdk">Syncfusion PDF Viewer</a>.</p><p>Users can open PDFs stored in SharePoint and use supported viewing, annotation, and review capabilities without leaving the browser-based workflow.</p><h3>Supported document experiences at a glance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*q0g04F2hB_3SMzfIP_GrDw.png" /></figure><p>Available operations depend on the corresponding document experience and deployment configuration.</p><h3>Collaborate on document processes</h3><p>SharePoint document scenarios often involve multiple users. A Word document may move between authors and reviewers. A workbook may need updates from several team members. A PDF may require annotations before approval.</p><p>BoldDocServer supports collaboration for applicable Word, Excel, and PDF experiences when the required collaboration services are enabled and configured. The exact collaboration experience depends on the document type and the capabilities enabled for the deployment.</p><h3>Keep SharePoint in control of documents and permissions</h3><p>For organizations already invested in SharePoint Server, an important question is whether replacing the document-editing layer also means changing the way documents are stored or secured.</p><p>With BoldDocServer, <strong>SharePoint remains the document repository and source of document permissions</strong>.</p><p>When a document is opened, SharePoint and BoldDocServer communicate through the configured WOPI workflow. The user’s effective access determines whether the document can be edited or should be opened with restricted access.</p><p>For example, when a user does not have permission to modify a document, editing operations can be restricted accordingly. This lets organizations introduce a new browser-based document experience without moving responsibility for document permissions away from SharePoint.</p><h3>How BoldDocServer works with SharePoint</h3><p>The process can be summarized in five steps.</p><h3>1. Select a document</h3><p>A user chooses a supported document from SharePoint.</p><h3>2. Open the document experience</h3><p>SharePoint initiates the configured WOPI action and opens the corresponding BoldDocServer experience in the browser.</p><h3>3. Access the document</h3><p>BoldDocServer communicates with SharePoint through the configured WOPI workflow to access the file.</p><h3>4. View, edit, or review</h3><p>The user works with the document through the corresponding Syncfusion document experience. Collaborative editing is available where supported and configured.</p><h3>5. Save supported changes</h3><p>Supported changes are saved back to SharePoint through the configured save-back process.</p><p>A simplified architecture looks like this: SharePoint Server connects through WOPI to BoldDocServer, which serves the DOCX Editor, Spreadsheet Editor and PDF Viewer as a browser-based document experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/0*Xhn0wJAaE4mW6xDl.png" /></figure><p>Throughout the process, SharePoint remains responsible for document storage and permissions.</p><h3>Why BoldDocServer matters for SharePoint teams</h3><p>Office Online Server retirement creates an opportunity to review browser-based document experiences that may have been operating unchanged for years.</p><p>For teams planning to continue with SharePoint Server, that review should answer questions such as:</p><ul><li>Which Office Online Server workloads are business-critical?</li><li>Which document types are frequently edited in the browser?</li><li>Which collaboration and review features are required?</li><li>Which SharePoint permission behaviors must remain unchanged?</li><li>How much infrastructure change is acceptable?</li><li>How early should a replacement environment be tested?</li></ul><p>BoldDocServer gives organizations another option when the requirement is to retain SharePoint Server while continuing supported browser-based document experiences.</p><h3>Who should evaluate BoldDocServer?</h3><p>BoldDocServer is especially relevant to organizations that:</p><ul><li>Currently use Office Online Server with SharePoint Server.</li><li>Plan to continue using SharePoint Server beyond December 31, 2026.</li><li>Need browser-based Word and Excel editing.</li><li>Need PDF viewing, annotation, or review as part of SharePoint document scenarios.</li><li>Want SharePoint to remain responsible for document storage and permissions.</li><li>Need a WOPI-based browser document experience.</li><li>Want to test a replacement before Office Online Server reaches retirement.</li></ul><p>Organizations with business-critical Office Online Server workloads should consider beginning their evaluation well before the deadline.</p><h3>Is BoldDocServer a complete replacement for every Office Online Server workload?</h3><p>Not necessarily. BoldDocServer is specifically designed around SharePoint Server document scenarios involving supported Word, Excel, and PDF experiences.</p><p>If your organization uses Office Online Server with other Microsoft server products or for workloads outside SharePoint, evaluate those dependencies separately as part of your transition plan.</p><p>This distinction helps ensure that migration planning reflects the actual workloads used within your environment.</p><h3>Start planning before the deadline</h3><p>December 31, 2026, may still leave some planning time, but enterprise infrastructure changes involve more than installing a replacement product.</p><p>A practical evaluation can follow these steps:</p><ol><li><strong>Inventory your current Office Online Server workloads</strong>: Identify the SharePoint sites, document types, departments, and business processes that depend on browser-based document access.</li><li><strong>Confirm your required document capabilities</strong>: Separate essential editing, review, and collaboration scenarios from features that are rarely used.</li><li><strong>Deploy BoldDocServer in a test environment</strong>: Begin with a test SharePoint farm or test site rather than changing production immediately.</li><li><strong>Configure and validate the WOPI integration</strong>: Verify document opening, permissions, editing, reviewing, and save-back behavior.</li><li><strong>Test representative Word, Excel, and PDF files</strong>: Use realistic documents from your organization’s existing scenarios.</li><li><strong>Validate permissions and multiuser scenarios</strong>: Test users with different SharePoint permission levels and collaboration requirements.</li><li><strong>Plan production rollout before Office Online Server retirement</strong>: Leave enough time for technical validation, security review, user testing, and operational preparation.</li></ol><p>The goal should not simply be to replace one server with another. It should be to verify that the document processes your organization depends on continue to operate as expected.</p><h3>Frequently Asked Questions</h3><ol><li><strong>What is BoldDocServer?<br></strong>BoldDocServer is a Syncfusion product that connects SharePoint Server with supported browser-based Word, Excel, and PDF experiences through WOPI. SharePoint continues to manage document storage and permissions.</li><li><strong>Why is Syncfusion introducing BoldDocServer now?<br></strong>Microsoft Office Online Server reaches the end of support on December 31, 2026. BoldDocServer gives organizations that plan to continue using SharePoint Server another option for supported browser-based document experiences.</li><li><strong>Is BoldDocServer an Office Online Server alternative?<br></strong>For supported SharePoint Server document viewing, editing, review, and collaboration scenarios, BoldDocServer is designed as an alternative browser-document layer.<br>Organizations using Office Online Server for workloads outside SharePoint should evaluate those scenarios separately.</li><li><strong>Which document formats does BoldDocServer support?<br></strong>BoldDocServer supports DOCX, DOC, DOTX, DOCM, DOTM, DOT files for Word documents, XLSX, XLS, CSV, XLSM, XLSB files for Excel workbooks, and PDF viewing with supported annotation and review operations.</li><li><strong>Does BoldDocServer replace SharePoint Server?<br></strong>No. SharePoint continues to store documents, manage permissions, and handle repository operations. BoldDocServer provides the browser-based document experience through WOPI.</li><li><strong>Can users save documents back to SharePoint?<br></strong>Yes, supported changes can be saved back to SharePoint through the configured WOPI workflow. Available save operations depend on the document type, supported capabilities, and deployment configuration.</li><li><strong>Does BoldDocServer support collaboration?<br></strong>BoldDocServer supports collaboration for applicable document scenarios when the required collaboration services and features are enabled and configured. The exact behavior depends on the document type and deployment configuration.</li><li><strong>When does Office Online Server support end?<br></strong>Microsoft lists December 31, 2026 as the retirement date for Office Online Server.</li><li><strong>When should organizations begin evaluating a replacement?<br></strong>Organizations that rely on Office Online Server should begin evaluating their options before the retirement date so they have enough time to inventory document scenarios, test documents, validate SharePoint permissions and WOPI integration, and prepare for production rollout.</li></ol><h3>Explore BoldDocServer</h3><p>Office Online Server support ends on December 31, 2026, but organizations do not need to wait until the deadline to decide what comes next.</p><p>BoldDocServer gives SharePoint Server teams a new option for browser-based Word, Excel, and PDF experiences while keeping SharePoint at the center of document storage and permissions.</p><p>If your organization expects to continue using SharePoint Server after Office Online Server retires, now is a good time to evaluate your document requirements and test your transition plan.</p><p>Explore <a href="https://www.bolddocserver.com/">BoldDocServer</a>, <a href="https://www.bolddocserver.com/downloads/confirm/">start a free trial</a>, and follow the <a href="https://docs.bolddocserver.com/quick-start.html">Quick Start</a> and <a href="https://docs.bolddocserver.com/sharepoint-integration.html">SharePoint Integration</a> guides to evaluate it with your SharePoint environment.</p><h3>Related Blogs</h3><ul><li><a href="https://www.syncfusion.com/blogs/post/document-processing-2026-volume-3-update">Syncfusion Document SDKs 2026 Volume 3: New JavaScript Libraries and Faster Excel Processing</a></li><li><a href="https://www.syncfusion.com/blogs/post/whats-new-2026-vol-3-document-solutions">Struggling with Complex Document Tasks? Explore Syncfusion Essential Studio 2026 Volume 3</a></li><li><a href="https://www.syncfusion.com/blogs/post/how-to-compare-pdf-documents-in-javascript-using-syncfusion-pdf-viewer">How to Compare PDF Documents in JavaScript Using Syncfusion PDF Viewer</a></li><li><a href="https://www.syncfusion.com/blogs/post/automate-document-processing-net">7 Document Automation Tasks Every .NET Application Should Handle Server-Side</a></li></ul><p><em>Originally published at </em><a href="https://www.syncfusion.com/blogs/post/introducing-bolddocserver-sharepoint"><em>https://www.syncfusion.com</em></a><em> on November 12, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=461d6a083ed8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/syncfusion/introducing-bolddocserver-an-office-online-server-alternative-for-sharepoint-server-461d6a083ed8">Introducing BoldDocServer: An Office Online Server Alternative for SharePoint Server</a> was originally published in <a href="https://medium.com/syncfusion">Syncfusion, Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Syncfusion Essential Studio Adds Day-One Support for .NET 11 | Syncfusion Blogs]]></title>
            <link>https://medium.com/syncfusion/syncfusion-essential-studio-adds-day-one-support-for-net-11-syncfusion-blogs-47fd2a04ed9e?source=rss----f6ee85f5a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/47fd2a04ed9e</guid>
            <category><![CDATA[blazor]]></category>
            <category><![CDATA[document-sdk]]></category>
            <category><![CDATA[net-maui]]></category>
            <category><![CDATA[net11]]></category>
            <category><![CDATA[csharp15]]></category>
            <dc:creator><![CDATA[Jollen Moyani]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 09:28:21 GMT</pubDate>
            <atom:updated>2026-11-12T09:28:20.632Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Syncfusion Essential Studio Adds Day-One Support for .NET 11 | Syncfusion Blogs" src="https://cdn-images-1.medium.com/max/1000/0*vsKREck5uJv1askA.png" /></figure><h3>Syncfusion Essential Studio Adds Day-One Support for .NET 11</h3><blockquote><strong>TL;DR:</strong> Syncfusion Essential Studio now supports .NET 11 from day one across .NET MAUI, Blazor, WPF, WinForms, WinUI, and Document SDK libraries. Developers can begin evaluating and upgrading supported Syncfusion applications to .NET 11 while taking advantage of the latest runtime, framework, tooling, and C# 15 capabilities.</blockquote><h3>.NET 11 is here and Syncfusion Essential Studio is ready</h3><p><a href="https://devblogs.microsoft.com/dotnet/announcing-dotnet-11/">.NET 11</a> is now generally available, bringing updates across the .NET runtime, C# 15, ASP.NET Core and Blazor, .NET MAUI, Windows development, libraries, tooling, and AI development.</p><p>For teams maintaining production applications, however, a new .NET release brings an immediate practical question:</p><p><strong>Are the UI components and document-processing libraries our applications depend on ready for the new runtime?</strong></p><p>With day-one .NET 11 support, Syncfusion® <a href="https://www.syncfusion.com/ui-component-suite">Essential Studio</a> enables developers to begin evaluating the new release without waiting for a later compatibility update across supported Syncfusion platforms.</p><p>That includes applications built with:</p><ul><li><a href="https://www.syncfusion.com/maui-controls">.NET MAUI</a></li><li><a href="https://www.syncfusion.com/blazor-components">Blazor</a></li><li><a href="https://www.syncfusion.com/wpf-controls">WPF</a></li><li><a href="https://www.syncfusion.com/winforms-ui-controls">WinForms</a></li><li><a href="https://www.syncfusion.com/winui-controls">WinUI</a></li><li><a href="https://www.syncfusion.com/document-sdk">Syncfusion Document SDK libraries</a></li></ul><p>Upgrading a production application still requires testing your own dependencies, application scenarios, deployment environment, and Microsoft’s .NET 11 breaking changes. Day-one support means the Syncfusion compatibility layer is available when you begin that evaluation.</p><p>Let’s look at what .NET 11 support means for Syncfusion developers, the framework changes worth knowing about, and the steps to consider when upgrading.</p><h3>Syncfusion .NET 11 support at a glance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*nYXH8B6F6qpBwYSm6ZdMWw.png" /></figure><p>If your application uses more than one Syncfusion package or platform dependency, update the related packages together and validate the complete application before deploying the .NET 11 build to production.</p><h3>What day-one .NET 11 support means for developers</h3><p>Framework compatibility involves more than changing the target framework and rebuilding.</p><p>A .NET application can depend on UI components, document libraries, third-party packages, native dependencies, publishing modes, operating-system capabilities, and application-specific requirements.</p><p>When evaluating .NET 11, consider the complete application.</p><h3>Update supported packages</h3><p>Use <a href="https://www.nuget.org/profiles/SyncfusionInc">Syncfusion NuGet</a> package versions that support .NET 11 and keep related Syncfusion packages aligned.</p><h3>Review .NET 11 breaking changes</h3><p>Review Microsoft’s <a href="https://learn.microsoft.com/en-us/dotnet/core/compatibility/11">compatibility and breaking changes</a> documentation for the frameworks and APIs your application uses.</p><h3>Test platform-specific behavior</h3><p>Validate behavior that matters to your application, such as:</p><ul><li>Data loading and editing.</li><li>Filtering and sorting.</li><li>Virtualization.</li><li>Charts and visualization.</li><li>Forms and validation.</li><li>Scheduling.</li><li>Themes and styling.</li><li>Printing and export.</li><li>Document generation and conversion.</li></ul><h3>Retest business-critical scenarios</h3><p>A successful build does not confirm that every application scenario behaves exactly as it did previously.</p><p>Run your application’s unit, integration, UI, regression, and performance tests against representative workloads before production deployment.</p><h3>.NET 11 highlights that matter for Syncfusion developers</h3><p>.NET 11 includes a large number of changes across the ecosystem.</p><p>Rather than reproducing the complete .NET 11 release notes, here are some of the changes particularly relevant to developers building UI-heavy and enterprise applications with Syncfusion.</p><h3>.NET MAUI: CoreCLR, XAML, and developer productivity</h3><p>One of the most significant changes in .NET 11 for .NET MAUI is the move to <strong>CoreCLR as the default runtime</strong> across supported MAUI platforms.</p><p>For developers, this brings the MAUI runtime closer to the broader .NET ecosystem and contributes to improvements in areas such as debugging, profiling, performance, and development experience.</p><p>.NET 11 also continues improving the XAML development experience.</p><p>Highlights include:</p><ul><li>Improvements to XAML source generation.</li><li>Better binding diagnostics.</li><li>Lazy ResourceDictionary loading.</li><li>XAML Incremental Hot Reload improvements.</li><li>Improvements for compiled bindings.</li><li>Additional controls and platform capabilities.</li><li>Testing and accessibility improvements.</li></ul><p>The framework also includes enhancements to maps, animations, CollectionView behavior, and native platform experiences.</p><h4>What this means for Syncfusion .NET MAUI developers</h4><p>Syncfusion <a href="https://www.syncfusion.com/maui-controls">.NET MAUI controls</a> support .NET 11, so existing applications can evaluate the new runtime while continuing to use controls such as <a href="https://www.syncfusion.com/maui-controls/maui-datagrid">DataGrid</a>, <a href="https://www.syncfusion.com/scheduler-sdk/maui-scheduler">Scheduler</a>, <a href="https://www.syncfusion.com/maui-controls/maui-cartesian-charts">Charts</a>, and other Syncfusion UI components.</p><p>When upgrading, test the scenarios most important to your application.</p><p>For example:</p><ul><li>DataGrid grouping, filtering, editing, and virtualization.</li><li>Scheduler navigation and interactions.</li><li>Chart rendering and updates.</li><li>Large datasets.</li><li>Device-specific layouts.</li><li>Application startup and navigation.</li><li>Existing XAML and binding behavior.</li></ul><h3>Blazor: Better forms, virtualization, and agentic UI experiences</h3><p>.NET 11 adds several capabilities to Blazor and ASP.NET Core that are relevant to data-driven enterprise applications.</p><h4>Improved form validation</h4><p>Blazor static server-side rendering forms gain improved client-side and asynchronous validation capabilities.</p><p>For applications with complex forms, this makes it easier to provide immediate validation while supporting rules that depend on remote APIs or other asynchronous operations.</p><h4>Better virtualization</h4><p>The Virtualize component receives improvements for items with different heights and adds capabilities for controlling scrolling and viewport behavior.</p><p>These improvements can be useful in interfaces such as:</p><ul><li>Chat experiences.</li><li>Activity feeds.</li><li>Logs.</li><li>Large dynamic lists.</li></ul><h4>Static SSR improvements</h4><p>.NET 11 expands static SSR capabilities, including improvements around caching, session-related scenarios, and state management.</p><h4>Agentic UI development</h4><p>.NET 11 also advances the AI application story for Blazor.</p><p>Microsoft is introducing experimental capabilities for building richer agentic interfaces, including scenarios where applications can stream AI output, render tool interactions, manage approvals, and coordinate UI state with AI agents.</p><p>For Syncfusion Blazor developers, this expands the range of AI-driven application experiences that can be explored alongside existing Syncfusion UI components.</p><h4>What this means for Syncfusion Blazor developers</h4><p>Syncfusion <a href="https://www.syncfusion.com/blazor-components">Blazor components</a> support .NET 11.</p><p>For applications using <a href="https://www.syncfusion.com/blazor-components/blazor-datagrid">DataGrid</a>, <a href="https://www.syncfusion.com/blazor-components/blazor-scheduler">Scheduler</a>, <a href="https://www.syncfusion.com/blazor-components/blazor-charts">Charts</a>, forms, dashboards, or other interactive components, validate:</p><ul><li>Data binding.</li><li>Sorting and filtering.</li><li>Virtualization.</li><li>Form validation.</li><li>Interactive render modes.</li><li>Export operations.</li><li>Authentication-related behavior.</li><li>Server and WebAssembly deployment scenarios used by your application.</li></ul><h3>Desktop development: WPF, WinForms, and WinUI</h3><p>.NET 11 also brings runtime, library, tooling, and Windows-development improvements relevant to desktop applications.</p><h4>Runtime and JIT improvements</h4><p>The .NET 11 runtime includes optimizations across JIT compilation, asynchronous operations, code generation, and core libraries.</p><p>These improvements can benefit applicable workloads, although the impact depends on the code paths and application.</p><h4>Runtime Async</h4><p>.NET 11 includes Runtime Async as a preview feature.</p><p>Runtime Async moves more of the mechanics behind asynchronous execution into the runtime, with goals including lower overhead and cleaner async stack traces.</p><p>Because it remains a preview capability, evaluate it separately before considering it for production application code.</p><h4>WinForms improvements</h4><p>.NET 11 includes improvements for Windows Forms across areas such as:</p><ul><li>Visual styling.</li><li>Full-screen and kiosk scenarios.</li><li>System visual settings.</li><li>Startup behavior.</li><li>Rendering and layout.</li><li>Input handling.</li></ul><h4>WPF improvements</h4><p>WPF receives reliability and rendering updates across several desktop scenarios.</p><h4>Syncfusion desktop controls</h4><p>Syncfusion <a href="https://www.syncfusion.com/wpf-controls">WPF</a>, <a href="https://www.syncfusion.com/winforms-ui-controls">WinForms</a>, and <a href="https://www.syncfusion.com/winui-controls">WinUI</a> controls support .NET 11.</p><p>When upgrading a desktop application, validate scenarios such as:</p><ul><li>DataGrid rendering and editing.</li><li>Chart updates.</li><li>Theming.</li><li>High-DPI behavior.</li><li>Keyboard and pointer interaction.</li><li>Printing.</li><li>Export.</li><li>Document viewing.</li><li>Window and layout behavior.</li></ul><h3>C# 15 comes with .NET 11</h3><p>C# 15 is the default language version for projects targeting .NET 11.</p><p>It introduces new language capabilities including:</p><ul><li>Collection expression arguments.</li><li>Union types.</li><li>Closed hierarchies.</li><li>Extension indexers.</li><li>Labeled break and continue.</li><li>Additional memory-safety work.</li></ul><p>These language features are independent of Syncfusion components, but developers can use supported C# 15 capabilities alongside Syncfusion applications targeting .NET 11.</p><p>As with any new language feature, evaluate whether it improves the clarity and maintainability of the specific application rather than adopting it simply because it is new.</p><h3>Syncfusion Document SDK libraries on .NET 11</h3><p>Syncfusion <a href="https://www.syncfusion.com/document-sdk">Document SDK libraries</a> also support .NET 11.</p><p>This means document-processing applications can evaluate the new runtime while continuing to use Syncfusion libraries for document-processing tasks involving formats such as <a href="https://www.syncfusion.com/document-sdk/net-pdf-library">PDF</a>, <a href="https://www.syncfusion.com/document-sdk/net-word-library">Word</a>, <a href="https://www.syncfusion.com/document-sdk/net-excel-library">Excel</a>, and <a href="https://www.syncfusion.com/document-sdk/net-powerpoint-library">PowerPoint</a>.</p><p>.NET 11 includes runtime and library optimizations that may benefit some document-processing workloads.</p><p>However, a newer runtime does not guarantee that every document operation becomes faster.</p><p>The performance difference depends on factors including:</p><ul><li>The document operation.</li><li>Input-file size and complexity.</li><li>Memory allocation behavior.</li><li>Runtime execution paths.</li><li>Application concurrency.</li><li>Publishing configuration.</li><li>Hardware.</li><li>Syncfusion package version.</li></ul><p>Our internal validation showed lower execution times in several selected Document SDK operations on .NET 11, while some operations showed little or no difference compared with .NET 10.</p><p>The important takeaway is not that every operation receives the same improvement.</p><p>If document-processing performance matters to your application, benchmark your own representative files and workloads on both runtimes before making performance assumptions.</p><h3>How to upgrade a Syncfusion application to .NET 11</h3><p>The exact upgrade process depends on your application platform, but this provides a practical starting point.</p><h3>1. Install the .NET 11 SDK and compatible development tools</h3><p>Install the final .NET 11 SDK and ensure that your development and CI environments use compatible tooling.</p><p>Verify the installed SDKs with:</p><pre>dotnet --list-sdks</pre><p>Avoid mixing preview and final SDK versions between developer machines and CI unless that configuration is intentional.</p><h3>2. Update the target framework</h3><p>Update the project’s target framework to the appropriate .NET 11 target framework moniker for your application type.</p><p>For a standard .NET application, for example:</p><pre>&lt;TargetFramework&gt;net11.0&lt;/TargetFramework&gt;</pre><p>Windows desktop and .NET MAUI projects use the corresponding platform-specific target frameworks.</p><p>Follow Microsoft’s platform documentation for the exact TFM required by your application.</p><h3>3. Update Syncfusion packages</h3><p>Update to Syncfusion package versions that support .NET 11.</p><p>For applications using multiple Syncfusion packages, keep compatible package versions aligned instead of updating individual dependencies in isolation.</p><h3>4. Restore packages and workloads</h3><p>Restore the application dependencies and any required platform workloads.</p><pre>dotnet restore</pre><p>For platforms such as .NET MAUI, make sure the corresponding .NET 11 workloads are installed and up to date.</p><h3>5. Review breaking changes</h3><p>Check Microsoft’s <a href="https://learn.microsoft.com/en-us/dotnet/core/compatibility/11">.NET 11 compatibility documentation</a> for changes relevant to:</p><ul><li>Runtime behavior.</li><li>ASP.NET Core.</li><li>.NET MAUI.</li><li>WPF.</li><li>WinForms.</li><li>Libraries.</li><li>SDK and tooling.</li></ul><p>Also review application-specific third-party dependencies before upgrading production projects.</p><h3>6. Build the application</h3><p>Perform a clean build and resolve any compilation, package, workload, or analyzer issues.</p><h3>7. Run regression tests</h3><p>Test the application scenarios your users actually depend on.</p><p>Do not treat a successful build as the end of the upgrade validation.</p><h3>What should you test before moving to production?</h3><p>The validation checklist depends on the platform.</p><h3>.NET MAUI</h3><p>Test:</p><ul><li>Startup.</li><li>Navigation.</li><li>DataGrid behavior.</li><li>Charts.</li><li>Scheduler.</li><li>XAML bindings.</li><li>Large datasets.</li><li>Device-specific layouts.</li><li>Android, iOS, Windows, and macOS scenarios your application supports.</li></ul><h3>Blazor</h3><p>Test:</p><ul><li>Server and WebAssembly scenarios you use.</li><li>Forms and validation.</li><li>Data loading.</li><li>Virtualization.</li><li>Authentication.</li><li>Grid operations.</li><li>Export.</li><li>Interactive components.</li><li>Reconnection and server-state behavior where applicable.</li></ul><h3>WPF, WinForms, and WinUI</h3><p>Test:</p><ul><li>Rendering.</li><li>Editing.</li><li>Themes.</li><li>High-DPI displays.</li><li>Accessibility.</li><li>Printing.</li><li>Export.</li><li>Keyboard and pointer input.</li><li>Window behavior.</li></ul><h3>Document SDK</h3><p>Test representative:</p><ul><li>PDF operations.</li><li>Word conversions.</li><li>Excel imports and exports.</li><li>PowerPoint operations.</li><li>Large files.</li><li>Concurrent processing.</li><li>Memory consumption.</li><li>Production deployment configuration.</li></ul><p>Whenever performance is important, measure the application using the files, hardware, concurrency, and deployment model that reflect your actual production workload.</p><h3>Should you move to .NET 11 immediately?</h3><p>.NET 11 is a <strong>Standard Term Support (STS)</strong> release.</p><p>Whether you should upgrade immediately depends on your organization’s requirements.</p><p>.NET 11 may be a good fit when you want:</p><ul><li>Access to the latest framework and runtime capabilities.</li><li>The newest .NET MAUI and Blazor improvements.</li><li>C# 15.</li><li>Current AI and agentic development capabilities.</li><li>The latest runtime and tooling improvements.</li></ul><p>Organizations that prioritize a longer support window may decide to remain on a supported LTS release depending on their lifecycle requirements.</p><p>The important point is that <strong>Syncfusion’s .NET 11 support lets you make that decision based on your application strategy rather than waiting for component compatibility</strong>.</p><h3>Frequently asked questions</h3><p><strong>Q1: Does Syncfusion Essential Studio support .NET 11?</strong></p><p>Yes. Syncfusion Essential Studio provides .NET 11 support across .NET MAUI, Blazor, WPF, WinForms, WinUI, and Document SDK libraries.</p><p><strong>Q2: Which Syncfusion platforms support .NET 11?</strong></p><p>The support covered in this release includes .NET MAUI, Blazor, WPF, WinForms, WinUI, and Syncfusion Document SDK libraries.</p><p><strong>Q3: Do I need to rewrite my Syncfusion application to move to .NET 11?</strong></p><p>Not necessarily, but every application should be evaluated individually.</p><p>Retarget the application, update compatible Syncfusion and third-party packages, review Microsoft’s breaking changes, and run regression tests against your important application scenarios.</p><p><strong>Q4: Does .NET 11 automatically make Syncfusion applications faster?</strong></p><p>No. .NET 11 contains runtime and JIT optimizations that can improve applicable workloads, but actual results depend on the application, data, hardware, operation, and deployment environment.</p><p>Measure performance using representative workloads before drawing conclusions.</p><p><strong>Q5: Is Runtime Async production-ready in .NET 11?</strong></p><p>Runtime Async is available in .NET 11 as a preview feature. Evaluate it separately before using it for production-specific application code.</p><p><strong>Q6: Does .NET 11 use C# 15?</strong></p><p>Yes. C# 15 is the default language version for projects targeting .NET 11 with the .NET 11 SDK.</p><p><strong>Q7: Is .NET 11 an LTS release?</strong></p><p>No. .NET 11 is a Standard Term Support (STS) release. Organizations should consider their support-lifecycle requirements when deciding between .NET 11 and a supported LTS release.</p><h3>Get started with Syncfusion and .NET 11</h3><p>.NET 11 brings updates across runtime performance, developer tooling, C# 15, .NET MAUI, Blazor, desktop development, core libraries, and AI application development.</p><p>With day-one .NET 11 support across Syncfusion Essential Studio UI components and Document SDK libraries, developers can begin evaluating these capabilities within their existing Syncfusion development environments.</p><p>If you’re planning an upgrade:</p><ul><li>Install the final <a href="https://dotnet.microsoft.com/en-us/download/dotnet/11.0">.NET 11 SDK</a>.</li><li>Update to the <a href="https://www.nuget.org/profiles/SyncfusionInc">Syncfusion packages</a> that support .NET 11.</li><li>Retarget the application.</li><li>Review breaking changes.</li><li>Build and test representative workloads.</li><li>Validate production-critical behavior before deployment.</li></ul><p>Explore the latest Syncfusion Essential Studio release from your Syncfusion <a href="https://www.syncfusion.com/account">license and download</a> page.</p><p>If you have questions while upgrading, use the Syncfusion <a href="https://www.syncfusion.com/forums">support forum</a>, <a href="https://support.syncfusion.com/">support portal</a>, or <a href="https://www.syncfusion.com/feedback/">feedback portal</a>.</p><h3>Related Blogs</h3><ul><li><a href="https://www.syncfusion.com/blogs/post/csharp-15-union-types-api-results">C# 15 Union Types for API Results: Examples, Trade-Offs, and Migration</a></li><li><a href="https://www.syncfusion.com/blogs/post/document-processing-2026-volume-3-update">Syncfusion Document SDKs 2026 Volume 3: New JavaScript Libraries and Faster Excel Processing</a></li><li><a href="https://www.syncfusion.com/blogs/post/syncfusion-essential-studio-2026-vol-3">What’s New in Syncfusion Essential Studio 2026 Volume 3: A2UI, New JavaScript Document Libraries, and More</a></li><li><a href="https://www.syncfusion.com/blogs/post/net-maui-smart-pdf-viewer-with-ai-assistance">Build AI-Powered PDF Workflows in .NET MAUI with Smart PDF Viewer</a></li></ul><p><em>Originally published at </em><a href="https://www.syncfusion.com/blogs/post/syncfusion-dotnet-11-support"><em>https://www.syncfusion.com</em></a><em> on November 11, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47fd2a04ed9e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/syncfusion/syncfusion-essential-studio-adds-day-one-support-for-net-11-syncfusion-blogs-47fd2a04ed9e">Syncfusion Essential Studio Adds Day-One Support for .NET 11 | Syncfusion Blogs</a> was originally published in <a href="https://medium.com/syncfusion">Syncfusion, Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Generate PDF Tables in JavaScript (PDF Grid) Using Syncfusion PDF Library]]></title>
            <link>https://medium.com/syncfusion/generate-pdf-tables-in-javascript-pdf-grid-using-syncfusion-pdf-library-06276f6f636b?source=rss----f6ee85f5a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/06276f6f636b</guid>
            <category><![CDATA[pdf-table]]></category>
            <category><![CDATA[file-format]]></category>
            <category><![CDATA[pdf]]></category>
            <category><![CDATA[document-processing]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Rajeshwari Pandinagarajan]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 04:50:16 GMT</pubDate>
            <atom:updated>2026-11-11T04:50:16.554Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Generate PDF Tables Using JavaScript PDF Grid" src="https://cdn-images-1.medium.com/max/1024/0*DVGZNhD2KVbAAYQ4.png" /></figure><blockquote><strong>TL;DR:</strong> Working with PDF tables in JavaScript involves handling dynamic data, formatting, and pagination. The new PDF Grid feature in Syncfusion JavaScript PDF Library provides a structured API with data binding, custom styling, hyperlinks, nested tables, and automatic pagination. Learn how to use these capabilities for invoices, reports, and other data-driven documents.</blockquote><p>Creating a PDF table involves more than arranging data into rows and columns. Consider generating an invoice with customer details, product information, tax calculations, and payment summaries. A simple table might be enough initially. But what happens when the invoice spans multiple pages, requires different cell styles, or includes links to related documents?</p><p>These requirements make PDF table generation more than a simple formatting task. Developers also need to manage layout, content, and pagination.</p><p>To simplify this process, Syncfusion® introduced the new PDF Grid feature in its <a href="https://www.syncfusion.com/document-sdk/javascript-pdf-library">JavaScript PDF Library</a> with <a href="https://help.syncfusion.com/common/essential-studio/release-notes/v35.1.37">Essential Studio 2026 Volume 3</a>. It provides a structured API for generating and customizing PDF tables.</p><p>In this guide, you’ll learn how to generate PDF tables from application data, customize their appearance, add interactive elements, and manage large datasets and multi-page layouts.</p><h3>Why PDF tables matter</h3><p>Most business applications eventually need to generate documents that contain structured data. Whether you’re exporting information for customers, internal teams, or compliance purposes, tables are often the easiest way to present large amounts of information clearly.</p><p>Common examples include:</p><ul><li>Invoices showing products, pricing, taxes, and totals.</li><li>Financial reports containing transactions and budget data.</li><li>Order summaries with shipment and payment information.</li><li>Inventory reports for stock monitoring and auditing.</li><li>Operational reports generated from business systems.</li></ul><h3>PDF Grid feature</h3><p>The Syncfusion JavaScript PDF Library now includes the PDF Grid feature, which provides a structured API for generating and customizing PDF tables. It supports data binding, custom styling, hyperlinks, nested tables, and automatic pagination, helping developers create tables for invoices, reports, and other data-driven PDF documents without manually managing every layout detail.</p><p>By handling these common table-generation requirements through a structured API, PDF Grid reduces the need for manual layout management and simplifies the process of creating complex PDF tables.</p><p>With PDF Grid, you can:</p><ul><li>Generate tables directly from application data.</li><li>Define rows and columns manually when needed.</li><li>Apply built-in styling to improve readability.</li><li>Add hyperlinks and images to table cells.</li><li>Create nested tables for hierarchical information.</li><li>Automatically paginate large datasets.</li><li>Handle tables that exceed page width.</li></ul><p>These capabilities are particularly useful when building invoices, reports, statements, audit logs, and other document-heavy business applications.</p><h3>Generate PDF tables from data</h3><p>In most applications, the data already exists in APIs, databases, or business objects. The real challenge is transforming that data into a readable PDF without manually creating every row and cell.</p><p>PDF Grid allows you to bind data directly to a table structure, making it easier to generate consistent reports from changing application data.</p><p>For example, if you’re generating a customer report every day, the table structure remains the same while the underlying data changes. Instead of rebuilding the layout each time, you simply supply updated data and regenerate the document.</p><h3>Configure the PDF Library</h3><p>Before generating PDF tables, add the Syncfusion <a href="https://help.syncfusion.com/document-processing/pdf/pdf-library/javascript/overview">JavaScript PDF Library</a> to your application.</p><h4>Step 1: Add the CDN reference</h4><pre>&lt;head&gt;<br>  &lt;!-- JavaScript PDF Library (CDN) --&gt;<br>  &lt;script src=&quot;https://cdn.syncfusion.com/ej2/35.1.37/dist/ej2.min.js&quot;&gt;&lt;/script&gt;<br>&lt;/head&gt;</pre><p><strong>Note:</strong> PDF Grid is available starting from Syncfusion Essential Studio 2026 Volume 3. Ensure you are using the corresponding Syncfusion JavaScript PDF Library version or later before running the examples in this article.</p><h4>Step 2: Serve the application</h4><p>Run your project using a local web server, such as:</p><pre>npx serve</pre><h4>Step 3: Start creating PDF documents</h4><p>Once the library is loaded, you can access the <strong>ej.pdf</strong> namespace to create PDF documents and generate PDF tables directly in the browser.</p><pre>// Create a new PDF document<br>var pdfDocument = new ej.pdf.PdfDocument();<br><br>// Add a page<br>var page = pdfDocument.addPage();<br><br>// Create the data source<br>var dataSource = [<br>    { id: &#39;E01&#39;, name: &#39;Clay&#39; },<br>    { id: &#39;E02&#39;, name: &#39;Thomas&#39; }<br>];<br><br>// Define the column mappings<br>var columns = [<br>    { field: &#39;id&#39;, headerText: &#39;Employee ID&#39;, width: 90 },<br>    { field: &#39;name&#39;, headerText: &#39;Employee Name&#39;, width: 140 }<br>];<br><br>// Create and draw the grid<br>var grid = new ej.pdf.PdfGrid(dataSource, columns);<br>var result = grid.draw(page, { x: 10, y: 10 });<br><br>// Save and close the document<br>pdfDocument.save(&#39;Output.pdf&#39;);<br>pdfDocument.destroy();</pre><figure><img alt="Creating a PDF table using JavaScript PDF Library" src="https://cdn-images-1.medium.com/max/1000/0*mdliBRcrSQ46dYyZ.png" /><figcaption>Creating a PDF table using JavaScript PDF Library</figcaption></figure><h3>Generate customer invoices</h3><p>Consider an order management application that generates PDF invoices.</p><p>Each invoice may contain:</p><ul><li>Customer information</li><li>Product line items</li><li>Quantities and pricing</li><li>Discounts and taxes</li><li>Payment summaries</li></ul><p>While a small invoice may fit on a single page, larger orders can span multiple pages and include dozens of rows.</p><h3>Apply built-in styles</h3><p>Good table design isn’t just about appearance. Clear formatting helps users process information faster and reduces errors when reviewing reports or invoices.</p><p>Rather than manually styling every element, you can apply built-in styles that format headers, rows, borders, and colors consistently across your document.</p><pre>// Create a new PDF document<br>var pdfDocument = new ej.pdf.PdfDocument();<br><br>// Add a page to the document<br>var page = pdfDocument.addPage();<br><br>// Create the data source<br>var source = [{ id: &#39;E01&#39;, name: &#39;Clay&#39; }, { id: &#39;E02&#39;, name: &#39;Thomas&#39; }];<br><br>// Define columns<br>var columns = [{ field: &#39;id&#39;, headerText: &#39;ID&#39; }, { field: &#39;name&#39;, headerText: &#39;Name&#39; }];<br><br>// Create grid with a built-in style applied<br>var grid = new ej.pdf.PdfGrid(source, columns, { builtInStyle: ej.pdf.PdfGridBuiltinStyle.gridTable4Accent1 });<br><br>// Draw the grid on the page<br>grid.draw(page, { x: 10, y: 10 });<br><br>// Save the document as Output.pdf<br>pdfDocument.save(&#39;Output.pdf&#39;);<br><br>// Dispose of the document resources<br>pdfDocument.destroy();</pre><p>Refer to the following image.</p><figure><img alt="Creating PDF table using built-in styles" src="https://cdn-images-1.medium.com/max/1000/0*D1W1gGOwgB_SZv5I.png" /><figcaption>Creating PDF table using built-in styles</figcaption></figure><h3>Customize PDF Tables</h3><p>Every document has different presentation requirements.</p><p>For example:</p><ul><li>Financial reports often require precise alignment.</li><li>Inventory reports may use conditional formatting.</li><li>Internal dashboards may include images and visual indicators.</li><li>Customer-facing documents often follow company branding guidelines.</li></ul><p>PDF Grid provides customization options for rows, columns, and individual cells, allowing you to tailor table layouts without manually drawing PDF content.</p><p>Additional customization features include:</p><ul><li>Row and column spanning</li><li>Custom cell formatting</li><li>Image insertion within cells</li><li>Table-wide styling options</li></ul><p>The following example customizes column widths, text alignment, row height, and cell styling:</p><pre>// Create the data source<br>var source = [{ id: &#39;E01&#39;, name: &#39;John&#39; }, { id: &#39;E02&#39;, name: &#39;Thomas&#39; }];<br><br>// Define columns with alignment and width settings<br>var columns = [<br>    {<br>        field: &#39;id&#39;, headerText: &#39;Employee ID&#39;, width: 80,<br>        style: { textProperties: {<br>            // Center horizontally and vertically<br>            horizontalAlignment: ej.pdf.PdfTemplateHorizontalAlignment.center,<br>            verticalAlignment: ej.pdf.PdfTemplateVerticalAlignment.middle<br>        } }<br>    },<br>    { field: &#39;name&#39;, headerText: &#39;Employee Name&#39;, width: 150 }<br>];<br><br>// Create grid from data source and columns<br>var grid = new ej.pdf.PdfGrid(source, columns);<br><br>// Customize the first row: set height to 50<br>grid.getRow(0).height = 50;<br><br>// Apply style to the first row<br>grid.getRow(0).style = {<br>    // Set light yellow background<br>    background: new ej.pdf.PdfBrush({ r: 255, g: 255, b: 200 }),<br>    textProperties: {<br>        // Set courier font with size 10<br>        font: new ej.pdf.PdfStandardFont(ej.pdf.PdfFontFamily.courier, 10),<br>        // Set text color to blue<br>        color: new ej.pdf.PdfBrush({ r: 0, g: 0, b: 255 })<br>    }<br>};</pre><figure><img alt="Creating PDF tables using customization options" src="https://cdn-images-1.medium.com/max/1000/0*3u2HElbyMCeBjM0m.png" /><figcaption>Creating PDF tables using customization options</figcaption></figure><h3>Add hyperlinks to PDF tables</h3><p>PDF documents often serve as more than static reports. In many cases, users need quick access to related resources, product pages, downloadable files, or internal documentation.</p><p>Instead of forcing users to copy and paste URLs manually, you can embed hyperlinks directly inside table cells and create a more interactive document experience.</p><p>The following example adds hyperlinks to PDF table cells:</p><pre>// Create a new PDF document<br>var pdfDocument = new ej.pdf.PdfDocument();<br><br>// Add a page to the document<br>var page = pdfDocument.addPage();<br><br>// Define column widths<br>var widths = new Map([[0, 130], [1, 180]]);<br><br>// Create rows with hyperlinks<br>var rows = [<br>    { cells: [<br>        { value: &#39;Product page&#39; },<br>        // Cell with external link<br>        { value: &#39;Syncfusion&#39;, link: { type: ej.pdf.PdfLinkType.externalLink, uri: &#39;https://www.syncfusion.com&#39; } }<br>    ] },<br>    { cells: [<br>        { value: &#39;Report&#39; },<br>        // Cell with file link<br>        { value: &#39;Open file&#39;, link: { type: ej.pdf.PdfLinkType.file, uri: &#39;Report.pdf&#39; } }<br>    ] }<br>];<br><br>// Create grid with 2 columns<br>var grid = new ej.pdf.PdfGrid(2, widths, rows);<br><br>// Draw the grid on the page<br>grid.draw(page, { x: 10, y: 10 });<br><br>// Save the document as Output.pdf<br>pdfDocument.save(&#39;Output.pdf&#39;);<br><br>// Dispose of the document resources<br>pdfDocument.destroy();</pre><p><strong>Note:</strong> File links require the target file to be available at the specified path when the PDF is opened.</p><figure><img alt="Adding hyperlinks in PDF tables using JavaScript PDF Grid" src="https://cdn-images-1.medium.com/max/1000/0*KjJJ7_Wb0B7JhsQx.png" /><figcaption>Adding hyperlinks in PDF tables using JavaScript PDF Grid</figcaption></figure><h3>Create nested PDF tables</h3><p>Not all data fits neatly into a flat table structure.</p><p>Imagine generating a sales report where each order contains multiple products. Trying to represent that information on a single table can quickly become difficult to read.</p><p>Nested PDF tables make these scenarios easier by allowing related data to remain grouped together. This approach works especially well for:</p><ul><li>Invoice line items</li><li>Order details</li><li>Product breakdowns</li><li>Project task hierarchies</li><li>Parent-child business records</li></ul><p>Refer to the following code example.</p><pre>// Create a new PDF document<br>var pdfDocument = new ej.pdf.PdfDocument();<br><br>// Add a page to the document<br>var page = pdfDocument.addPage();<br><br>// Create the nested grid (inner table)<br>var childGridWidths = new Map([[0, 80], [1, 100]]);<br>var childGridRows = [<br>    { cells: [{ value: &#39;Product&#39; }, { value: &#39;Quantity&#39; }] },<br>    { cells: [{ value: &#39;Keyboard&#39; }, { value: &#39;2&#39; }] },<br>    { cells: [{ value: &#39;Mouse&#39; }, { value: &#39;1&#39; }] }<br>];<br><br>// Create the nested grid instance<br>var childGrid = new ej.pdf.PdfGrid(2, childGridWidths, childGridRows);<br><br>// Create the parent grid (outer table)<br>var parentWidths = new Map([[0, 100], [1, 200]]);<br>var parentRows = [{<br>    cells: [<br>        { value: &#39;Order details&#39; },<br>        // Embed the nested grid as a cell value<br>        { value: childGrid }<br>    ]<br>}];<br><br>// Create the parent grid instance<br>var parentGrid = new ej.pdf.PdfGrid(2, parentWidths, parentRows);<br><br>// Draw the parent grid (which includes the nested grid)<br>parentGrid.draw(page, { x: 10, y: 10 });<br><br>// Save the document as Output.pdf<br>pdfDocument.save(&#39;Output.pdf&#39;);<br><br>// Dispose of the document resources<br>pdfDocument.destroy();</pre><figure><img alt="Creating nested tables using JavaScript PDF Grid" src="https://cdn-images-1.medium.com/max/1000/0*DtBsUO95DvdbFn0o.png" /><figcaption>Creating nested tables using JavaScript PDF Grid</figcaption></figure><p>Want to build advanced table layouts? Learn more about nested PDF tables in the PDF Grid <a href="https://help.syncfusion.com/document-processing/pdf/pdf-library/javascript/tables#add-a-nested-table">documentation</a>.</p><h3>Handle large PDF tables</h3><p>Generating a PDF is often easy.</p><p>Generating a PDF that remains readable when it contains hundreds of rows or dozens of columns is where things become challenging.</p><p>Large reports typically create two common problems:</p><ol><li>The table exceeds the page width.</li><li>The table exceeds the page height.</li></ol><p>The new JavaScript PDF Grid includes features for both scenarios, helping developers avoid manual layout calculations.</p><h3>Manage table width</h3><p>Business reports often contain many columns, especially when displaying analytics, inventory data, or operational metrics.</p><p>Rather than shrinking all content until it becomes unreadable, PDF Grid provides multiple <a href="https://ej2.syncfusion.com/documentation/api/pdf/pdfgridhorizontaloverflowtype">overflow modes</a> that allow wide tables to continue across additional pages.</p><ul><li><strong>onePage (default)</strong>: Fits all columns within the available page width by scaling the table to a single page.</li><li><strong>nextPage</strong>: Moves overflowing columns to subsequent pages while maintaining row correspondence across pages.</li><li><strong>lastPage</strong>: Groups all overflowing columns and renders them together on a single continuation page.</li></ul><p>This flexibility helps you display wide datasets without manually splitting tables or adjusting column layouts.</p><p>The following example moves overflowing columns to additional pages when the table exceeds the available page width:</p><pre>// Create a new PDF document<br>var pdfDocument = new ej.pdf.PdfDocument();<br><br>// Add the first page<br>var firstPage = pdfDocument.addPage();<br><br>// Create the grid<br>var grid = new ej.pdf.PdfGrid(<br>    createEmployeeRows(40),<br>    createEmployeeColumns()<br>);<br><br>// Enable horizontal overflow to the next page<br>grid.horizontalOverflow = ej.pdf.PdfGridHorizontalOverflowType.nextPage;<br><br>// Repeat header rows on overflow pages<br>grid.repeatHeader = true;<br><br>// Configure pagination settings<br>var format = new ej.pdf.PdfLayoutFormat();<br>format.layout = ej.pdf.PdfLayoutType.paginate;<br>format.break = ej.pdf.PdfLayoutBreakType.fitPage;<br><br>// Draw the grid<br>grid.draw(<br>    firstPage,<br>    {<br>        x: 10,<br>        y: 10<br>    },<br>    format<br>);<br><br>// Save the document<br>pdfDocument.save(&#39;Output.pdf&#39;);<br><br>// Dispose resources<br>pdfDocument.destroy();<br><br>function createEmployeeColumns() {<br>    return [<br>        { field: &#39;employeeId&#39;, headerText: &#39;Employee ID&#39;, width: 75 },<br>        { field: &#39;firstName&#39;, headerText: &#39;First Name&#39;, width: 80 },<br>        { field: &#39;lastName&#39;, headerText: &#39;Last Name&#39;, width: 80 },<br>        { field: &#39;department&#39;, headerText: &#39;Department&#39;, width: 90 },<br>        { field: &#39;designation&#39;, headerText: &#39;Designation&#39;, width: 100 },<br>        { field: &#39;email&#39;, headerText: &#39;Email Address&#39;, width: 150 },<br>        { field: &#39;phone&#39;, headerText: &#39;Phone Number&#39;, width: 100 },<br>        { field: &#39;city&#39;, headerText: &#39;City&#39;, width: 80 },<br>        { field: &#39;state&#39;, headerText: &#39;State&#39;, width: 90 },<br>        { field: &#39;country&#39;, headerText: &#39;Country&#39;, width: 75 }<br>        // Additional employee columns can be added here.<br>    ];<br>}<br><br>function createEmployeeRows(rowCount) {<br>    return [<br>        {<br>            employeeId: &#39;EMP0001&#39;,<br>            firstName: &#39;Arun&#39;,<br>            lastName: &#39;Kumar&#39;,<br>            department: &#39;Engineering&#39;,<br>            designation: &#39;Software Engineer&#39;,<br>            email: &#39;arun.kumar@example.com&#39;,<br>            phone: &#39;+91 90000 10001&#39;,<br>            city: &#39;Chennai&#39;,<br>            state: &#39;Tamil Nadu&#39;,<br>            country: &#39;India&#39;<br>        }<br>        // Additional employee records can be added here.<br>    ];<br>}</pre><figure><img alt="Text overflow option in JavaScript PDF Grid" src="https://cdn-images-1.medium.com/max/1024/0*3FXOIg0aA2aGcCE6.gif" /><figcaption>Text overflow option in JavaScript PDF Grid</figcaption></figure><h3>Enable automatic pagination</h3><p>Manually managing page breaks is one of the most frustrating parts of PDF generation.</p><p>When reports contain hundreds or thousands of rows, developers often need to calculate page boundaries and repeat headers manually.</p><p>PDF Grid can automatically paginate tables while preserving readability and optionally repeat headers on continuation pages.</p><pre>// Create a new PDF document<br>var pdfDocument = new ej.pdf.PdfDocument();<br><br>// Add the first page<br>var page = pdfDocument.addPage();<br><br>// Create a large data source with 100 employee records<br>var source = [];<br>for (var i = 1; i &lt;= 100; i++) {<br>    source.push({ id: &#39;E&#39; + i, name: &#39;Employee &#39; + i });<br>}<br><br>// Define columns with widths<br>var columns = [{ field: &#39;id&#39;, headerText: &#39;ID&#39;, width: 80 }, { field: &#39;name&#39;, headerText: &#39;Name&#39;, width: 160 }];<br><br>// Create grid from data source and columns<br>var grid = new ej.pdf.PdfGrid(source, columns);<br><br>// Enable header repetition on continuation pages<br>grid.repeatHeader = true;<br><br>// Create a layout format for pagination<br>var format = new ej.pdf.PdfLayoutFormat();<br><br>// Set layout type to paginate (flow across pages)<br>format.layout = ej.pdf.PdfLayoutType.paginate;<br><br>// Set break type to fit entire page<br>format.break = ej.pdf.PdfLayoutBreakType.fitPage;<br><br>// Draw grid with pagination across multiple pages<br>var result = grid.draw(page, { x: 10, y: 10, width: 300, height: 500 }, format);<br><br>// Save the document as Output.pdf<br>pdfDocument.save(&#39;Output.pdf&#39;);<br><br>// Dispose of the document resources<br>pdfDocument.destroy();</pre><h3>Tips for large PDF reports</h3><p>When generating large PDF reports, a few practices can improve maintainability and readability:</p><ul><li>Use data binding when generating tables from APIs or databases.</li><li>Enable header repetition for multi-page reports.</li><li>Use nested tables only when hierarchical data is required.</li><li>Apply consistent styling to improve report readability.</li><li>Let pagination features handle page breaks instead of manually splitting datasets.</li></ul><p>Want to explore PDF Grid before implementing it in your application?</p><p>Check out the interactive <a href="https://document.syncfusion.com/demos/document-library/javascript/#/tailwind3/pdf/grid-drawing.html">demo</a> to see how the Syncfusion JavaScript PDF Library generates and customizes PDF tables.</p><h3>Frequently Asked Questions</h3><p>Q1: Can I create PDF tables manually without using a data source?</p><p>Absolutely. PDF Grid allows you to build tables manually by defining columns, headers, and rows in code. This approach is ideal when you need full control over the table structure or when your data isn’t available as a collection.</p><p>Q2: Can I add multiple PDF tables to the same page?</p><p>Yes. You can render multiple PDF tables on a single page. PDF Grid provides layout information after each table is drawn, making it easy to position additional tables without overlapping existing content.</p><p>Q3: Can I merge cells in a PDF table?</p><p>Yes. PDF Grid supports both row and column spanning, allowing you to merge cells and create more advanced layouts for grouped information, summary sections, invoices, and custom reports.</p><p>Q4: Can I insert images into PDF table cells?</p><p>Yes. Images can be added directly to table cells, with control over size, alignment, and fit mode. This makes it easy to create product catalogs, employee directories, inventory reports, and other visually rich PDF documents.</p><p>Q5: How can I create borderless PDF tables in JavaScript?</p><p>PDF Grid supports borderless table layouts by applying a zero-width border style at the grid level. This is useful when you want data to remain organized in rows and columns without displaying visible table borders.</p><p>Q6: Can I prevent table rows from splitting across multiple PDF pages?</p><p>Yes. By using <strong>PdfLayoutBreakType.fitElement</strong>, you can keep an entire row together on the same page. If a row doesn’t fit in the remaining space, it’s automatically moved to the next page, helping preserve readability and create more professional-looking documents.</p><h3>Simplify PDF table generation</h3><p>PDF Grid simplifies PDF table generation in <a href="https://www.syncfusion.com/document-sdk/javascript-pdf-library">JavaScript</a> by providing built-in support for data binding, styling, hyperlinks, nested tables, overflow handling, and pagination. Whether you’re creating invoices, reports, financial documents, or application exports, it helps you build professional PDF tables with less manual layout code and a consistent document structure.</p><p>If you’re evaluating approaches for PDF table generation in JavaScript, exploring the available <a href="https://document.syncfusion.com/demos/document-library/javascript/#/tailwind3/pdf/grid-drawing.html">examples</a> and <a href="https://help.syncfusion.com/document-processing/pdf/pdf-library/javascript/tables">documentation</a> can be a useful next step before implementing it in production applications.</p><p>This feature is available in our <a href="https://www.syncfusion.com/forums/198591/essential-studio-2026-volume-3-main-release-v35-1-37-is-available-for-download">2026 Volume 3</a> release. You can also explore the <a href="https://help.syncfusion.com/common/essential-studio/release-notes/v35.1.37">Release Notes</a> and <a href="https://www.syncfusion.com/products/whatsnew">What’s New</a> pages for additional details.</p><p>Existing customers can access these features through the <a href="https://www.syncfusion.com/sales/pricing">License and Downloads</a> page. New users can start a 30-day <a href="https://www.syncfusion.com/downloads/">free trial</a> to explore these features.</p><p>For queries, you can contact us through our <a href="https://www.syncfusion.com/forums">support forums</a>, <a href="https://support.syncfusion.com/">support portal</a>, or <a href="https://www.syncfusion.com/feedback">feedback portal</a>. We are always happy to assist you!</p><h3>Related blogs</h3><ul><li><a href="https://www.syncfusion.com/blogs/post/syncfusion-essential-studio-2026-vol-3">What’s New in Syncfusion Essential Studio 2026 Volume 3: A2UI, New JavaScript Document Libraries, and More</a></li><li><a href="https://www.syncfusion.com/blogs/post/pdf-signature-validation-javascript">How to Validate PDF Digital Signatures in JavaScript with Timestamps and Long-Term Validation (LTV)</a></li><li><a href="https://www.syncfusion.com/blogs/post/how-to-compare-pdf-documents-in-javascript-using-syncfusion-pdf-viewer">How to Compare PDF Documents in JavaScript Using Syncfusion PDF Viewer</a></li><li><a href="https://www.syncfusion.com/blogs/post/document-processing-2026-volume-3-update">Syncfusion Document SDKs 2026 Volume 3: New JavaScript Libraries and Faster Excel Processing</a></li></ul><p><em>Originally published at </em><a href="https://www.syncfusion.com/blogs/post/generate-pdf-table-in-javascript"><em>https://www.syncfusion.com</em></a><em> on November 10, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=06276f6f636b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/syncfusion/generate-pdf-tables-in-javascript-pdf-grid-using-syncfusion-pdf-library-06276f6f636b">Generate PDF Tables in JavaScript (PDF Grid) Using Syncfusion PDF Library</a> was originally published in <a href="https://medium.com/syncfusion">Syncfusion, Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build AI-Powered PDF Workflows in .NET MAUI with Smart PDF Viewer]]></title>
            <link>https://medium.com/syncfusion/build-ai-powered-pdf-workflows-in-net-maui-with-smart-pdf-viewer-34b4bdf20d14?source=rss----f6ee85f5a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/34b4bdf20d14</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[pdf]]></category>
            <category><![CDATA[desktop]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[cross-platform]]></category>
            <dc:creator><![CDATA[Rajeshwari Pandinagarajan]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 08:22:15 GMT</pubDate>
            <atom:updated>2026-11-09T08:22:15.593Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Build AI-Powered PDF Workflows in .NET MAUI with Smart PDF Viewer" src="https://cdn-images-1.medium.com/max/1024/0*gIvsDpdKWilX77h6.jpg" /></figure><h3>Build AI-Powered PDF Workflows in .NET MAUI with Smart PDF Viewer</h3><blockquote><strong>TL;DR:</strong> Want to make PDF workflows smarter in your .NET MAUI applications? The Syncfusion Smart PDF Viewer brings AI-powered document summarization, question answering, sensitive data redaction, and automatic form filling into one component. In this blog, learn how to integrate these features using Azure OpenAI and build more efficient document experiences across Android, iOS, macOS, and Windows.</blockquote><p>Working with PDFs often involves more than just viewing documents. You may need to find specific information, remove sensitive details, or fill out forms. Doing all this manually can take time, especially when working with large documents.</p><h3>What if your application could help users complete these tasks with AI?</h3><p>The Syncfusion® <a href="https://www.syncfusion.com/pdf-viewer-sdk/ai-powered-net-maui-pdf-viewer">AI-Powered .NET MAUI Smart PDF Viewer</a>, introduced in <a href="https://help.syncfusion.com/common/essential-studio/release-notes/v35.1.37">Essential Studio 2026 Volume 3</a>, makes this possible. It extends the PDF viewing experience with three AI-powered features: <a href="https://help.syncfusion.com/document-processing/pdf/smart-pdf-viewer/maui/document-summarizer">AI Assistant</a>, <a href="https://help.syncfusion.com/document-processing/pdf/smart-pdf-viewer/maui/smart-redaction">Smart Redaction</a>, and <a href="https://help.syncfusion.com/document-processing/pdf/smart-pdf-viewer/maui/smart-fill">Smart Form Fill</a>.</p><p>With these features, users can summarize documents, ask questions, identify sensitive information, and fill out PDF forms with less manual effort.</p><p>In this blog, we’ll explore these features and learn how to integrate the Smart PDF Viewer into a .NET MAUI application using Azure OpenAI.</p><h3>What can you do with the .NET MAUI Smart PDF Viewer?</h3><p>Imagine you’re building a customer onboarding application. Users need to review agreements, check customer details, and complete PDF forms before submitting them.</p><p>Instead of handling each task manually, you can use the Smart PDF Viewer to:</p><ul><li><strong>Understand documents:</strong> Generate summaries and ask questions about PDF content.</li><li><strong>Protect sensitive information:</strong> Find details such as names, email addresses, and phone numbers that need to be redacted.</li><li><strong>Complete PDF forms:</strong> Extract information from copied content and fill in the matching form fields.</li></ul><p>All these capabilities are available within the same PDF viewing experience.</p><p>Let’s look at each feature in detail.</p><h3>1. Understand lengthy documents with the AI Assistant</h3><p>Have you ever opened a lengthy PDF just to find one specific piece of information? Searching through every page can be frustrating.</p><p>The built-in <a href="https://help.syncfusion.com/document-processing/pdf/smart-pdf-viewer/maui/document-summarizer">AI Assistant</a> makes this easier. Users can generate a summary of a PDF, ask questions about its content, and explore suggested prompts.</p><p>For example, when reviewing a business report, users can ask questions such as:</p><ul><li>What are the key findings in this report?</li><li>Summarize the main points.</li><li>What are the important dates mentioned in this document?</li></ul><p>The AI Assistant analyzes the document and provides relevant responses, helping users find information without reading every page.</p><figure><img alt="AI Assistant for PDF summarization" src="https://cdn-images-1.medium.com/max/1024/0*ClzgAdhbYpiAN1l6.gif" /><figcaption>AI Assistant for PDF summarization</figcaption></figure><p><strong>Key capabilities include:</strong></p><ul><li>Generate concise summaries of lengthy documents.</li><li>Ask questions and get answers based on document content.</li><li>Explore suggested prompts to learn more about the document.</li><li>Understand reports, contracts, research papers, and technical documents more easily.</li></ul><p>This feature is useful whenever users need to understand large amounts of information quickly.</p><h3>2. Find and protect sensitive information with Smart Redaction</h3><p>PDF documents often contain information that shouldn’t be shared with everyone. This could include customer details, financial information, or personal identifiers.</p><p>Finding all these details manually can take time, particularly when a document contains many pages.</p><p>The <a href="https://help.syncfusion.com/document-processing/pdf/smart-pdf-viewer/maui/smart-redaction">Smart Redaction</a> feature helps simplify this process by using AI to identify sensitive information in PDF documents.</p><p>Users can select the information they want to detect, scan the document, review the results, and apply redaction to the selected content.</p><figure><img alt="AI-powered Smart Redaction" src="https://cdn-images-1.medium.com/max/1024/0*NfE4ImRtqvGHOzRM.gif" /><figcaption>AI-powered Smart Redaction</figcaption></figure><p>For example, when preparing a customer agreement for external sharing, users can look for:</p><ul><li>Person names</li><li>Organization names</li><li>Email addresses</li><li>Phone numbers</li><li>Credit card numbers</li><li>Other confidential information</li></ul><p>Developers can also configure custom detection patterns to identify information specific to their applications or business requirements.</p><p><strong>How does it work?</strong></p><ol><li><strong>Select patterns:</strong> Choose the types of sensitive information to identify.</li><li><strong>Scan the document:</strong> Let AI find matching information throughout the PDF.</li><li><strong>Review the results:</strong> Check the detected information in the Redaction panel.</li><li><strong>Apply redaction:</strong> Select the items to redact and confirm the changes.</li></ol><p>One important point: AI detection may not identify every sensitive detail correctly. Always review the detected items before applying redaction.</p><p>Also, applying redaction permanently removes the selected content. It cannot be recovered through undo or redo. Keep a backup of the original document when required.</p><h3>3. Fill PDF forms automatically with Smart Form Fill</h3><p>Filling out PDF forms often involves copying information from emails, spreadsheets, or other documents and entering it into the correct fields.</p><p>Imagine a user needs to complete a customer registration form. The customer details are already available in an email, but the user still has to enter each value manually.</p><p><a href="https://help.syncfusion.com/document-processing/pdf/smart-pdf-viewer/maui/smart-fill">Smart Form Fill</a> helps reduce this effort.</p><p>It uses AI to understand copied information and match the extracted values to the appropriate PDF form fields.</p><figure><img alt="Smart Form Fill" src="https://cdn-images-1.medium.com/max/1024/0*IWFSn1zNX5Dcp5mG.gif" /><figcaption>Smart Form Fill</figcaption></figure><p>For example, a user might copy the following customer details:</p><pre>Name: John Doe <br>Email: [email protected] <br>Phone: +1 555 0100</pre><p>Smart Form Fill analyzes the copied information and identifies the matching fields in the PDF form.</p><p>Instead of entering each value individually, users can let the feature populate the matching fields automatically.</p><p><strong>Key benefits include:</strong></p><ul><li>Extract information from copied content.</li><li>Match values with the appropriate PDF form fields.</li><li>Reduce repetitive data entry.</li><li>Complete forms more quickly.</li></ul><p>Smart Fill works with PDF documents containing form fields, such as text boxes, combo boxes, radio buttons, and list boxes. Users can review and adjust the populated values before finalizing the form.</p><h3>4. Connect your preferred AI provider</h3><p>Different applications may use different AI services depending on their existing architecture and requirements.</p><p>For example, your application might already use Azure OpenAI, OpenAI, or a custom AI service.</p><p>The .NET MAUI Smart PDF Viewer supports AI integration through the Microsoft.Extensions.AI chat client infrastructure. It also provides a custom integration approach through the IChatInferenceService interface.</p><p>This gives developers flexibility when connecting AI services to their applications.</p><p>You can integrate services such as:</p><ul><li>Azure OpenAI</li><li>OpenAI</li><li>Ollama</li><li>Gemini</li><li>Claude</li><li>DeepSeek</li><li>Groq</li></ul><p>For custom integrations, the IChatInferenceService interface provides a standard way to connect your AI service with Syncfusion Smart Components.</p><p>Refer to the <a href="https://help.syncfusion.com/document-processing/pdf/smart-pdf-viewer/maui/custom-ai-service">custom AI service integration guide</a> for implementation details.</p><p>Now, let’s see how to integrate Azure OpenAI with the Smart PDF Viewer.</p><h3>Get started with the .NET MAUI Smart PDF Viewer</h3><p>Let’s create a simple .NET MAUI application and add the Smart PDF Viewer with Azure OpenAI integration.</p><h3>Prerequisites</h3><p>Before getting started, make sure you have:</p><ul><li>.NET 10 SDK or later.</li><li>Visual Studio with .NET MAUI development support.</li><li>An Azure OpenAI resource with a deployed model.</li><li>An Azure OpenAI endpoint, deployment name, and API key.</li></ul><h3>Step 1: Create a .NET MAUI project</h3><p>First, create a new .NET MAUI application using the .NET CLI:</p><pre>dotnet new maui -n MauiSmartPdfViewerExample<br>cd MauiSmartPdfViewerExample</pre><p>This creates a new .NET MAUI project.</p><h3>Step 2: Install the required NuGet packages</h3><p>Next, install the following packages to add the Smart PDF Viewer and configure Azure OpenAI.</p><pre>Install-Package Syncfusion.Maui.SmartPdfViewer<br>Install-Package Microsoft.Extensions.AI<br>Install-Package Microsoft.Extensions.AI.OpenAI<br>Install-Package Azure.AI.OpenAI</pre><p>These packages provide the PDF Viewer component and the required AI integration.</p><h3>Step 3: Configure the Syncfusion services</h3><p>Open the MauiProgram.cs file and register the Syncfusion core services.</p><p>Add the following namespace:</p><pre>using Syncfusion.Maui.Core.Hosting;</pre><p>Then, configure the Syncfusion core handler in the CreateMauiApp method:</p><pre>public static class MauiProgram<br>{<br>    public static MauiApp CreateMauiApp()<br>    {<br>        var builder = MauiApp.CreateBuilder();<br>        builder<br>            .UseMauiApp&lt;App&gt;()<br>            .ConfigureFonts(fonts =&gt;<br>            {<br>                fonts.AddFont(&quot;OpenSans-Regular.ttf&quot;, &quot;OpenSansRegular&quot;);<br>            });<br>        // Register Syncfusion core services.<br>        builder.ConfigureSyncfusionCore();<br><br>        return builder.Build();<br>    }<br>}</pre><p>This registers the required Syncfusion services in your application.</p><h3>Step 4: Configure Azure OpenAI</h3><p>Now, let’s connect Azure OpenAI to the application.</p><p>First, add the following namespaces to MauiProgram.cs:</p><pre>using Azure.AI.OpenAI;<br>using Microsoft.Extensions.AI;<br>using Syncfusion.Maui.SmartComponents.Hosting;<br>using System.ClientModel;</pre><p>Inside the CreateMauiApp method, configure the Azure OpenAI client and register it with the dependency injection container.</p><pre>public static class MauiProgram<br>{<br>    public static MauiApp CreateMauiApp()<br>    {<br>        var builder = MauiApp.CreateBuilder();<br><br>        builder<br>            .UseMauiApp&lt;App&gt;()<br>            .ConfigureFonts(fonts =&gt;<br>            {<br>                fonts.AddFont(&quot;OpenSans-Regular.ttf&quot;, &quot;OpenSansRegular&quot;);<br>            });<br><br>        // Register Syncfusion core services.<br>        builder.ConfigureSyncfusionCore();<br><br>        // Azure OpenAI configuration.<br>        string azureOpenAiKey = &quot;api-key&quot;;<br>        string azureOpenAiEndpoint = &quot;endpoint URL&quot;;<br>        string azureOpenAiModel = &quot;deployment-name&quot;;<br><br>        // Create the Azure OpenAI client.<br>        AzureOpenAIClient azureOpenAiClient = new AzureOpenAIClient(<br>            new Uri(azureOpenAiEndpoint),<br>            new ApiKeyCredential(azureOpenAiKey));<br><br>        // Configure the chat client.<br>        IChatClient azureOpenAiChatClient = azureOpenAiClient<br>            .GetChatClient(azureOpenAiModel)<br>            .AsIChatClient();<br><br>        // Register the chat client.<br>        builder.Services.AddChatClient(azureOpenAiChatClient);<br><br>        // Register Syncfusion AI services.<br>        builder.ConfigureSyncfusionAIServices();<br><br>        return builder.Build();<br>    }<br>}</pre><p>Replace the placeholder values with your Azure OpenAI configuration:</p><ul><li>azureOpenAiKey: Your Azure OpenAI API key.</li><li>azureOpenAiEndpoint: Your Azure OpenAI endpoint URL.</li><li>azureOpenAiModel: Your deployed model name.</li></ul><p><strong>Security note:</strong> Avoid storing long-lived API keys directly in production client applications. Use a secure backend or an appropriate token-based authentication approach to protect your credentials.</p><p>The AddChatClient method registers the AI chat client with the dependency injection container. The Smart PDF Viewer uses this registered client for its AI-powered features.</p><p><strong>Note:</strong> The AI service configuration is required for document summarization, Smart Redaction, and Smart Fill. Basic PDF viewing does not require an AI service.</p><h3>Step 5: Add the Smart PDF Viewer</h3><p>Next, open the MainPage.xaml file and add the Syncfusion namespace:</p><pre>xmlns:syncfusion=&quot;clr-namespace:Syncfusion.Maui.SmartPdfViewer;assembly=Syncfusion.Maui.SmartPdfViewer</pre><p>Add the SfSmartPdfViewer control to the page:</p><pre>&lt;syncfusion:SfSmartPdfViewer<br>    x:Name=&quot;pdfViewer&quot;<br>    DocumentSource=&quot;{Binding PdfDocumentStream}&quot; /&gt;</pre><p>Here, DocumentSource specifies the PDF document stream to display in the viewer.</p><p>For this example, bind it to a PdfDocumentStream property in your view model. You can load a PDF from an embedded resource, local storage, or another supported document source.</p><h3>Step 6: Enable the AI-powered features</h3><p>Now, let’s configure the three AI-powered features in the Smart PDF Viewer.</p><h4>Enable the AI Assistant</h4><p>Use AssistViewSettings to configure document summarization and question-answering capabilities.</p><p>Add the following configuration inside the SfSmartPdfViewer control:</p><pre>&lt;syncfusion:SfSmartPdfViewer.AssistViewSettings&gt;<br>    &lt;syncfusion:AssistViewSettings<br>        Prompt=&quot;Summarize this document.&quot;<br>        Placeholder=&quot;Enter your query...&quot;<br>        ShowPromptSuggestions=&quot;True&quot; /&gt;<br>&lt;/syncfusion:SfSmartPdfViewer.AssistViewSettings&gt;</pre><p>Also, set IsAIAssistViewVisible to True on the viewer to display the AI Assistant panel.</p><p>Here is what these properties do:</p><ul><li>Prompt: Defines the initial prompt used to guide AI-generated responses.</li><li>Placeholder: Displays the placeholder text in the query input area.</li><li>ShowPromptSuggestions: Shows or hides suggested prompts.</li><li>IsAIAssistViewVisible: Shows or hides the AI Assistant panel.</li></ul><p>With this configuration, users can summarize PDF documents and ask questions about their content.</p><h4>Enable Smart Redaction</h4><p>Next, use SmartRedactSettings to enable AI-powered sensitive information detection.</p><pre>&lt;syncfusion:SfSmartPdfViewer.SmartRedactSettings&gt;<br>    &lt;syncfusion:SmartRedactSettings IsEnabled=&quot;True&quot; /&gt;<br>&lt;/syncfusion:SfSmartPdfViewer.SmartRedactSettings&gt;</pre><p>Set IsSmartRedactViewVisible to True on the viewer to display the Smart Redaction panel.</p><p>You can also configure custom detection patterns using the RedactPatterns property.</p><p>For example, add the following configuration in your C# code:</p><pre>pdfViewer.SmartRedactSettings = new SmartRedactSettings<br>{<br>    IsEnabled = true,<br>    RedactPatterns = new string[]<br>    {<br>        &quot;Person Names&quot;,<br>        &quot;Organization Names&quot;,<br>        &quot;Email Addresses&quot;,<br>        &quot;Phone Numbers&quot;,<br>        &quot;Credit Card Numbers&quot;<br>    }<br>};</pre><p>Here:</p><ul><li>IsEnabled: Enables or disables Smart Redaction.</li><li>RedactPatterns: Specifies the types of sensitive information to identify.</li><li>IsSmartRedactViewVisible: Controls the visibility of the Smart Redaction panel.</li></ul><p>You can replace the sample patterns with custom patterns based on your application’s requirements.</p><h4>Enable Smart Form Fill</h4><p>Finally, configure Smart Form Fill using the SmartFillSettings class.</p><pre>&lt;syncfusion:SfSmartPdfViewer.SmartFillSettings&gt;<br>    &lt;syncfusion:SmartFillSettings IsEnabled=&quot;True&quot; /&gt;<br>&lt;/syncfusion:SfSmartPdfViewer.SmartFillSettings&gt;</pre><p>The IsEnabled property controls whether Smart Fill is available in the viewer.</p><p>Once enabled, users can access Smart Fill from the AI Tools menu in the viewer toolbar. The option becomes available when the loaded PDF contains form fields.</p><p>You can also trigger Smart Fill programmatically.</p><p>To use the current clipboard content:</p><pre>await pdfViewer.ApplySmartFillAsync(<br>    CancellationToken.None);</pre><p>To provide custom text instead of using clipboard content:</p><pre>string customerDetails =<br>    &quot;Name: John Doe\n&quot; +<br>    &quot;Email: [email protected]\n&quot; +<br>    &quot;Phone: +1 555 0100&quot;;<br><br>await pdfViewer.ApplySmartFillAsync(<br>    customerDetails,<br>    CancellationToken.None);</pre><p>The viewer analyzes the supplied information and maps the extracted values to matching form fields.</p><h3>Step 7: Register the Syncfusion license</h3><p>Before using the Smart PDF Viewer, register your Syncfusion license key in MauiProgram.cs.</p><pre>Syncfusion.Licensing.SyncfusionLicenseProvider<br>    .RegisterLicense(&quot;YOUR_LICENSE_KEY&quot;);</pre><p>Replace the placeholder with your valid Syncfusion license key.</p><p>For more information, refer to the <a href="https://help.syncfusion.com/common/essential-studio/licensing/license-key">Syncfusion licensing documentation</a>.</p><h3>Step 8: Run the application</h3><p>You’re all set!</p><p>Build and run the application on your preferred target platform: Android, iOS, macOS, or Windows.</p><figure><img alt=".NET MAUI Smart PDF Viewer with AI tools enabled" src="https://cdn-images-1.medium.com/max/1000/0*3HnScudSHnl5jbhv.png" /><figcaption>.NET MAUI Smart PDF Viewer with AI tools enabled</figcaption></figure><p>Once the PDF document loads, you can try the AI-powered features:</p><ul><li>Generate summaries and ask questions using the AI Assistant.</li><li>Scan documents and redact sensitive information using Smart Redaction.</li><li>Populate PDF form fields using Smart Form Fill.</li></ul><p>You now have an AI-powered document experience integrated into your .NET MAUI application.</p><p><strong>Platform note</strong>: Android deployments may require additional semantic-search model setup for AI-powered features. Refer to the <a href="https://help.syncfusion.com/document-processing/pdf/smart-pdf-viewer/maui/getting-started">.NET MAUI Smart PDF Viewer getting-started documentation</a> for the platform-specific setup instructions.</p><h3>Frequently asked questions</h3><p><strong>Q: Which platforms are supported by the .NET MAUI Smart PDF Viewer?</strong></p><p><strong>A:</strong> The .NET MAUI Smart PDF Viewer supports Android, iOS, macOS, and Windows. You can use the same .NET MAUI codebase to build applications for these platforms.</p><p><strong>Q: Do I need an AI service to use the Smart PDF Viewer?</strong></p><p><strong>A: </strong>No. You can use the basic PDF viewing capabilities without configuring an AI service. However, features such as document summarization, Smart Redaction, and Smart Fill require a registered AI chat client.</p><p><strong>Q: What types of information can Smart Redaction identify?</strong></p><p><strong>A:</strong> Smart Redaction supports detection patterns for person names, organization names, email addresses, phone numbers, addresses, dates, account numbers, credit card numbers, and other configurable information. You can also define custom patterns based on your application requirements.</p><p><strong>Q: Can I use my own AI service?</strong></p><p><strong>A:</strong> Yes. The Smart PDF Viewer supports custom AI service integration through the IChatInferenceService interface. This allows you to connect your preferred AI service to Syncfusion Smart Components.</p><p><strong>Q: How does Smart Form Fill work?</strong></p><p><strong>A:</strong> Smart Form Fill analyzes clipboard content or supplied text, extracts relevant information, and maps the values to matching PDF form fields. It requires a PDF containing form fields and a configured AI service. Users can review and adjust the populated values before finalizing the form.</p><h3>Conclusion</h3><p>Working with PDF documents doesn’t have to involve repetitive manual tasks. With AI-powered features, users can find information, protect sensitive details, and complete forms more easily.</p><p>The Syncfusion <a href="https://www.syncfusion.com/pdf-viewer-sdk/ai-powered-net-maui-pdf-viewer">AI-Powered .NET MAUI Smart PDF Viewer</a> brings these capabilities together in one component. Its AI Assistant, Smart Redaction, and Smart Form Fill features help developers build more interactive document workflows across Android, iOS, macOS, and Windows.</p><p>You can also connect Azure OpenAI or integrate a custom AI service based on your application’s requirements.</p><p>Ready to try it in your application? Explore the <a href="https://help.syncfusion.com/document-processing/pdf/smart-pdf-viewer/maui/getting-started">.NET MAUI Smart PDF Viewer documentation</a> and get started with the <a href="https://www.syncfusion.com/account/manage-trials/start-trials">30-day free trial</a>.</p><p>If you have questions or feedback, connect with us through our <a href="https://www.syncfusion.com/forums">support forums</a> or <a href="https://www.syncfusion.com/feedback">feedback portal</a>.</p><h3>Related blogs</h3><p>· <a href="https://www.syncfusion.com/blogs/post/syncfusion-dotnet-maui-2026-volume-3">What’s New in Syncfusion .NET MAUI 2026 Volume 3: New Controls and Features</a></p><p>· <a href="https://www.syncfusion.com/blogs/post/maui-interactive-viewer-control">Introducing the .NET MAUI Interactive Viewer Control for Interactive Content</a></p><p>· <a href="https://www.syncfusion.com/blogs/post/fifth-set-open-source-maui-controls">Introducing the Fifth Set of Open-Source Syncfusion .NET MAUI Controls</a></p><p>· <a href="https://www.syncfusion.com/blogs/post/resizable-layouts-maui-grid-splitter">How to Build Resizable Layouts with the .NET MAUI Grid Splitter</a></p><p><em>Originally published at </em><a href="https://www.syncfusion.com/blogs/post/net-maui-smart-pdf-viewer-with-ai-assistance"><em>https://www.syncfusion.com</em></a><em> on November 6, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34b4bdf20d14" width="1" height="1" alt=""><hr><p><a href="https://medium.com/syncfusion/build-ai-powered-pdf-workflows-in-net-maui-with-smart-pdf-viewer-34b4bdf20d14">Build AI-Powered PDF Workflows in .NET MAUI with Smart PDF Viewer</a> was originally published in <a href="https://medium.com/syncfusion">Syncfusion, Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Validate PDF Digital Signatures in JavaScript with Timestamps and Long-Term Validation (LTV)…]]></title>
            <link>https://medium.com/syncfusion/how-to-validate-pdf-digital-signatures-in-javascript-with-timestamps-and-long-term-validation-ltv-e383eb157572?source=rss----f6ee85f5a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/e383eb157572</guid>
            <category><![CDATA[pdf]]></category>
            <category><![CDATA[digital-signatures]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Rajeshwari Pandinagarajan]]></dc:creator>
            <pubDate>Fri, 06 Nov 2026 13:01:00 GMT</pubDate>
            <atom:updated>2026-11-06T13:01:00.519Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="How to Validate PDF Digital Signatures in JavaScript with Timestamps and Long-Term Validation (LTV)" src="https://cdn-images-1.medium.com/max/1024/0*N6_gpB6qtU_NP1nx.png" /></figure><h3>How to Validate PDF Digital Signatures in JavaScript with Timestamps and Long-Term Validation (LTV)</h3><blockquote><strong>TL;DR:</strong> Need to verify signed PDFs long after signing? Learn how to digitally sign PDFs, add trusted timestamps, enable Long-Term Validation (LTV), and validate individual or multiple signatures using the Syncfusion JavaScript PDF Library.</blockquote><p>A digital signature helps verify who signed a PDF and whether the document has changed since signing. But how can you validate that signature months or even years later, especially when the signing certificate has expired, or revocation information is no longer available?</p><p>Trusted timestamps and Long-Term Validation (LTV) information help preserve the evidence needed for future signature verification.</p><p>With the <a href="https://help.syncfusion.com/common/essential-studio/release-notes/v35.1.37">2026 Volume 3 release</a>, Syncfusion® added digital signature validation and Long-Term Validation (LTV) capabilities in its <a href="https://www.syncfusion.com/document-sdk/javascript-pdf-library">JavaScript PDF Library</a>.</p><p>In this guide, you’ll learn how to:</p><ul><li>Sign PDF documents using a digital certificate.</li><li>Add a trusted timestamp from a Time Stamping Authority (TSA).</li><li>Enable Long-Term Validation (LTV).</li><li>Validate individual and multiple signatures.</li><li>Interpret validation results correctly.</li></ul><p><strong>Important:</strong> A trusted timestamp and LTV information can help preserve the evidence needed to validate a PDF signature in the future. However, successful long-term validation still depends on the signature’s integrity, the available certificate and revocation evidence, the certificate chain, and the trust policies used by the validating application. LTV improves future validation readiness but does not guarantee indefinite validation under all circumstances.</p><h3>What the new PDF validation capability enables</h3><p>The new validation capabilities allow developers to:</p><ul><li>Verify whether a signed document has been altered after signing.</li><li>Validate certificate chains used by signatures.</li><li>Inspect trusted timestamp information.</li><li>Check certificate revocation status using OCSP and CRL evidence.</li><li>Validate a specific signature field.</li><li>Validate multiple signatures in a single PDF document.</li><li>Support processes that require long-term signature verification.</li></ul><p>These capabilities are especially useful in document management, finance, legal, healthcare, government, and compliance-focused applications where document integrity must be preserved over time.</p><h3>Digitally sign a PDF in JavaScript</h3><p>Digital signatures help verify a PDF document’s authenticity, confirm the identity of the signer, and detect whether the document has been altered after signing. By applying a certificate-based digital signature, you can establish trust in electronic documents and support secure document processing.</p><p>Using the Syncfusion <a href="https://help.syncfusion.com/document-processing/pdf/pdf-library/javascript/digitalsignature">JavaScript PDF Library</a>, you can digitally sign both newly created and existing PDF documents with industry-standard certificates.</p><h3>Prerequisites</h3><p>Before you begin, ensure you have the following:</p><ul><li>A valid digital certificate (.PFX or .P12) containing the private key.</li><li>The certificate password.</li><li>A PDF document to sign, or a new PDF document to create.</li><li>The Syncfusion JavaScript PDF Library.</li></ul><p><strong>Security Consideration:</strong> Never hardcode PFX passwords, private keys, or certificate files in browser-delivered JavaScript. Private keys are sensitive cryptographic assets and should be protected appropriately. For high-security environments, consider server-side signing or a managed digital-signing service rather than exposing signing credentials to client applications.</p><p>Once your certificate and PDF document are ready, you can sign the document by creating a signature field, applying a digital signature, and saving the signed PDF.</p><h3>Steps to digitally sign a PDF</h3><h4>Step 1: Create or load a PDF document</h4><p>Create a new document or load an existing PDF, depending on your use case. The document acts as the container for the digital signature and related form fields.</p><h4>Step 2: Create a signature field</h4><p>Add a <a href="https://ej2.syncfusion.com/documentation/api/pdf/pdfsignaturefield">PdfSignatureField</a> to the document. This field defines where the signature information will be stored and displayed within the PDF.</p><h4>Step 3: Create and apply a digital signature</h4><p>Load the PFX certificate and create a <a href="https://ej2.syncfusion.com/documentation/api/pdf/pdfsignature">PdfSignature</a> object using the certificate and password. You can also specify the cryptographic standard and hashing algorithm used to generate the signature.</p><h4>Step 4: Add the signature field and save the document</h4><p>After applying the signature, add the signature field to the PDF form and save the document. The resulting PDF contains a verifiable digital signature that can later be validated for integrity and authenticity.</p><p>The following example creates a new PDF document, adds a signature field, and applies a digital signature using a PFX certificate and the SHA-256 hashing algorithm:</p><pre>// Create the document<br>var document = new ej.pdf.PdfDocument();<br>// Get the first page of the document<br>var page = document.addPage();<br>// Access the PDF form<br>var form = document.form;<br>// Create a new signature field<br>var field = new ej.pdf.PdfSignatureField(page, &#39;Signature&#39;, {x: 10, y: 10, width: 100, height: 50});<br>// Create a new signature using PFX data and private key<br>var sign = ej.pdf.PdfSignature.create(certData, password, {cryptographicStandard: ej.pdf.CryptographicStandard.cms, digestAlgorithm: ej.pdf.DigestAlgorithm.sha256});<br>// Set the signature to the field<br>field.setSignature(sign);<br>// Add the field to the PDF form<br>form.add(field);<br>// Draw the logo in the signature appearance <br>const signatureAppearance = field.getAppearance(); <br>const signatureImage = new PdfBitmap(logo); <br>signatureAppearance.normal.graphics.drawImage(signatureImage, { <br>    x: 20, <br>    y: 20, <br>    width: 120, <br>    height: 50 <br>}); <br>// Save the document<br>document.save(&#39;output.pdf&#39;);<br>// Destroy the document<br>document.destroy();</pre><figure><img alt="Adding a digital signature to a PDF" src="https://cdn-images-1.medium.com/max/1000/0*hgRhYefM5ycR2PGT.png" /><figcaption>Adding a digital signature to a PDF</figcaption></figure><p><strong>Note:</strong> In this example, <strong>certData</strong> represents the PFX certificate bytes and <strong>password</strong> is the certificate password. These values should be securely loaded through your application’s credential management process rather than embedded directly in source code.</p><p>For additional signing scenarios, including signing existing PDFs and advanced signature configuration options, explore the <a href="https://document.syncfusion.com/demos/document-library/javascript/#/tailwind3/pdf/digitalSignature.html">digital signature demo</a> and refer to the <a href="https://help.syncfusion.com/document-processing/pdf/pdf-library/javascript/digitalsignature?cs-save-lang=1&amp;cs-tab-name=JavaScript&amp;cs-lang=js#add-a-digital-signature-to-a-new-document">API documentation</a>.</p><h3>Add a trusted timestamp to a PDF signature</h3><p>A timestamp records when a document was signed through a trusted Time Stamping Authority (TSA). It provides evidence of the signing time and helps support future signature verification.</p><p>To add a timestamp, provide a timestamp callback when creating the digital signature. The callback returns the TSA response, which is embedded into the signature during the save operation.</p><p>The following example shows how to add a timestamp to a digitally signed PDF document. Apply the returned signature to the signature field before saving, as in the signing example above.</p><pre>// Create a timestamp callback<br>async function timestampCallback(request) {<br>    // Implement timestamp response logic here<br>    return { response: new Uint8Array() }; // Placeholder return<br>}<br>// Create a new signature using PFX data, private key and callback function for timestamp<br>const signature = ej.pdf.PdfSignature.create(certData, password, { cryptographicStandard: ej.pdf.CryptographicStandard.cms, digestAlgorithm: ej.pdf.DigestAlgorithm.sha256 }, timestampCallback);<br>field.setSignature(signature);<br>// Save the document<br>await document.saveAsync(&#39;output.pdf&#39;);</pre><figure><img alt="Adding a timestamp to a digitally signed PDF document" src="https://cdn-images-1.medium.com/max/1000/0*j4nbnZHnnaASAERX.png" /><figcaption>Adding a timestamp to a digitally signed PDF document</figcaption></figure><p><strong>Note:</strong> This example demonstrates the callback contract only. Your application must send the timestamp request to a trusted Time Stamping Authority (TSA) and return the TSA response bytes.</p><h3>Why use saveAsync()?</h3><p>When timestamping is enabled, the library must communicate with an external TSA service. Because the operation is asynchronous, use <strong>await document.saveAsync()</strong> to ensure that the timestamp response is received and embedded before the PDF is generated.</p><p>For a complete timestamp integration example, refer to the <a href="https://help.syncfusion.com/document-processing/pdf/pdf-library/javascript/digitalsignature?cs-save-lang=1&amp;cs-tab-name=JavaScript&amp;cs-lang=js#adding-a-timestamp-in-digital-signature">digital signature documentation</a>.</p><h3>Enhance PDF signature validation with Long-Term Validation (LTV)</h3><p>A trusted timestamp helps establish when a document was signed, but long-term verification often requires additional evidence. If certificate revocation services become unavailable, validators may not be able to retrieve the information needed to determine whether the signing certificate was trusted at the time of signing.</p><p>Long-Term Validation (LTV) helps address this challenge by embedding certificate and revocation information directly into the PDF.</p><p>To enable LTV:</p><ul><li>Sign and save the PDF.</li><li>Reload the signed document.</li><li>Retrieve the signature.</li><li>Call the enableLTV() method and provide revocation responses through the callback.</li></ul><p>The following code example demonstrates how to enable LTV for a signed PDF document.</p><pre>// Load the signed PDF document<br>const document = new ej.pdf.PdfDocument(data);<br>// Get the signature field<br>const field = document.form.fieldAt(0);<br>// Retrieve the PDF signature<br>const signature = field.getSignature();<br>// Retrieve the OCSP or CRL response requested by the library<br>var longTermValidationCallback = async function (url, requestBytes) {<br>    // Send requestBytes to the approved URL and return the actual response bytes<br>    return { response: revocationResponse };<br>};<br>// Enable LTV for the created signature<br>var ltvEnabled = await signature.enableLTV(longTermValidationCallback);<br>// Save the LTV-enabled PDF document<br>document.save(&#39;output.pdf&#39;);</pre><p><strong>Note:</strong> This callback must return the actual OCSP or CRL response bytes requested by the library. Network communication, authentication, retry logic, and error handling should be implemented by your application.</p><p>After you enable LTV, the PDF contains additional validation information that can support future verification and archival processes.</p><p>For complete LTV examples and implementation guidance, refer to the <a href="https://help.syncfusion.com/document-processing/pdf/pdf-library/javascript/digitalsignature?cs-save-lang=1&amp;cs-tab-name=JavaScript&amp;cs-lang=js#long-term-validation-ltv">LTV documentation</a>.</p><h3>Validate PDF signatures</h3><p>Once a signed PDF contains timestamp and optional LTV information, the next step is validation. Validation helps determine whether the document has been modified after signing and whether the associated certificates, timestamps, and revocation information remain trustworthy.</p><p>The Syncfusion JavaScript PDF Library supports validation for both individual signatures and multiple signatures contained within a PDF document.</p><p>During validation, the library can verify document modifications, certificate chains, timestamp information, revocation status through OCSP or CRL data, and multiple signatures available in the document.</p><figure><img alt="Validating PDF signatures using the Syncfusion JavaScript PDF Library" src="https://cdn-images-1.medium.com/max/983/0*6proa-4PNvhaMcBW.png" /><figcaption>Validating PDF signatures using the Syncfusion JavaScript PDF Library</figcaption></figure><h3>Validation prerequisites</h3><p>Before validating signatures, prepare the following:</p><ul><li><strong>documentData:</strong> The PDF document bytes to validate.</li><li><strong>certificateData:</strong> Trusted root or intermediate certificate data used to establish trust.</li><li><strong>passwords:</strong> Optional passwords used only when validating encrypted PDFs or password-protected processes.</li></ul><p>Providing a certificate does not automatically establish trust. Validation depends on whether a complete and trusted certificate chain can be successfully built according to your organization’s trust requirements.</p><h3>Validate a single signature</h3><p>To validate an individual signature, retrieve the associated signature field and call the <strong>validateSignature()</strong> method. The validation process checks whether the document has been modified after signing and evaluates certificate trust, timestamp validity, and revocation status based on the specified validation options.</p><p>The following example validates a single signature using trusted certificate information:</p><pre>// Load the signed PDF document.<br>const document = new ej.pdf.PdfDocument(documentData);<br>// Get the first signature field from the form.<br>const field = document.form.fieldAt(0);<br>// Configure the signature validation options.<br>const options = {<br>    trustedCertificates: [certificateData],<br>    passwords: [&#39;syncfusion&#39;]<br>};<br>// Validate the signature.<br>const validationResult = field.validateSignature(options);<br>// Check the validation result.<br>console.log(&#39;Signature name: &#39; + validationResult.signatureName);<br>console.log(&#39;Signature valid: &#39; + validationResult.isSignatureValid);<br>console.log(&#39;Signature status: &#39; + validationResult.signatureStatus);<br>console.log(&#39;Document modified: &#39; + validationResult.isDocumentModified);<br>console.log(&#39;Revocation result: &#39;, validationResult.revocationResult);<br>// Destroy the document and release its resources.<br>document. Destroy();</pre><p>The returned validation result contains details about signature validity, document integrity, certificate-chain validation, timestamp verification, and revocation checks.</p><p>Include the passwords option only when validating encrypted PDFs or processes that require password-protected content.</p><p>Note: Explore the <a href="https://document.syncfusion.com/demos/document-library/javascript/#/tailwind3/pdf/digital-signature-validation.html">digital signature validation demo</a> to see the validation process in action and review the validation results returned by the <a href="https://help.syncfusion.com/document-processing/pdf/pdf-library/javascript/digitalsignature#digital-signature-validation">API</a>.</p><h3>Validate multiple signatures in a PDF</h3><p>When a PDF contains multiple signatures, validate them collectively using the <strong>validateSignatures()</strong> method. The method evaluates every signature field in the document and returns both overall and signature-specific validation results.</p><p>The following example validates all signatures in a PDF document:</p><pre>// Load the PDF document that contains multiple signatures.<br>const document = new ej.pdf.PdfDocument(documentData);<br>// Configure the validation options.<br>const options = {<br>    trustedCertificates: [certificateData]<br>    passwords: [&#39;syncfusion&#39;]<br>};<br>// Validate all signatures in the PDF document.<br>const validationResult = document.form.validateSignatures(options);<br>if (validationResult.results !== null &amp;&amp;<br>    validationResult.results !== undefined) {<br>    console.log(<br>        &#39;Number of validated signatures: &#39; +<br>        validationResult.results.length<br>    );<br>    validationResult.results.forEach((result) =&gt; {<br>        console.log(<br>            `${result.signatureName}: ${result.isSignatureValid}`<br>        );<br>    });<br>}<br>// Determine whether all signatures are valid.<br>if (validationResult.isValid) {<br>    console.log(&#39;All signatures in the PDF document are valid.&#39;);<br>} else {<br>    console.log(&#39;One or more signatures in the PDF document are invalid.&#39;);<br>}</pre><p>The <strong>validationResult.isValid</strong> property indicates the overall validation outcome for the document. Review the entries in <strong>validationResult.results</strong> to inspect the status of each individual signature.</p><p><strong>Note:</strong> For additional validation scenarios, review the digital signature validation <a href="https://document.syncfusion.com/demos/document-library/javascript/#/tailwind3/pdf/digital-signature-validation.html">demo</a> and <a href="https://help.syncfusion.com/document-processing/pdf/pdf-library/javascript/digitalsignature#digital-signature-validation">documentation</a>. They include examples covering certificate validation, revocation checking, timestamp verification, and multi-signature validation processes.</p><h3>Understanding validation results</h3><p>The <strong>validationResult.isValid</strong> property represents the overall validation outcome based on the validation options you supplied.</p><p>However, developers should also review the individual entries in <strong>validationResult.results</strong>, since each signature may have different validation outcomes for:</p><ul><li>Certificate trust.</li><li>Timestamp verification.</li><li>Revocation status.</li><li>Certificate-chain validation.</li><li>Document integrity.</li></ul><p>Reviewing individual validation results provides a more complete assessment than relying only on a single Boolean value. It also helps you make more informed trust decisions when processing signed PDF documents.</p><h3>Build a trusted PDF signing and validation process</h3><p>Now that we’ve covered signing, timestamping, LTV, and validation individually, let’s see how they fit together in a complete process.</p><p>Creating a trusted PDF process involves more than simply applying a digital signature. To ensure long-term document reliability, follow this recommended sequence:</p><ol><li>Sign the PDF to establish document authenticity and integrity.</li><li>Add a trusted timestamp to record when the document was signed.</li><li>Enable LTV to embed revocation information required for future verification.</li><li>Validate the signature before accepting, sharing, or archiving the document.</li></ol><p>Following this process helps preserve the evidence needed to validate signed PDF documents after certificate expiration or when external revocation services are unavailable.</p><h3>Recommended process</h3><ul><li>Step 1: Sign the PDF using <a href="https://ej2.syncfusion.com/documentation/api/pdf/pdfsignature">PdfSignature.create()</a>.</li><li>Step 2: Add a timestamp using a TSA callback and <a href="https://ej2.syncfusion.com/documentation/api/pdf/pdfdocument#saveasync">saveAsync()</a>.</li><li>Step 3: Reload the signed document and enable LTV using <a href="https://ej2.syncfusion.com/documentation/api/pdf/pdfsignature#enableltv">enableLTV()</a>.</li><li>Step 4: Validate the signature using validateSignature() or <a href="https://ej2.syncfusion.com/documentation/api/pdf/pdfform#validatesignatures">validateSignatures()</a>.</li></ul><p>In production environments, these four stages represent the complete trust lifecycle of a signed PDF document. Each stage adds verification evidence that helps preserve trust beyond the initial signing event.</p><p>By combining these stages, you can build secure and reliable PDF signing processes for contracts, compliance documents, business records, and other long-term digital documents.</p><h3>Frequently Asked Questions</h3><p><strong>Q: Why is a basic digital signature not enough for long-term PDF trust?</strong></p><p>Certificates can expire, and revocation information may not always be available in the future. Without a trusted timestamp and Long-Term Validation (LTV), signature validation may lack the evidence required to verify the document over time.</p><p><strong>Q: What does a signature timestamp prove?</strong></p><p>A trusted Time Stamping Authority (TSA) provides evidence of when a document was signed. This timestamp can help establish that the signature existed at a particular time and support verification against the signing certificate’s validity period.</p><p><strong>Q: What is LTV in PDF digital signatures?</strong></p><p>Long-Term Validation (LTV) embeds revocation information, such as OCSP and CRL responses, directly into the PDF. This helps support signature validation even when external revocation services are unavailable.</p><p>Q: Does the JavaScript PDF Library support PDF digital signing?</p><p>Yes. The Syncfusion JavaScript PDF Library supports certificate-based digital signatures for both new and existing PDF documents through the PdfSignature and PdfSignatureField classes.</p><p><strong>Q: Can LTV and timestamps be used together?</strong></p><p>Yes. You can add a timestamp when creating the digital signature and then enable Long-Term Validation (LTV) after signing to support long-term signature verification.</p><p><strong>Q: How are signatures validated with the library?</strong></p><p>Use <strong>signature.validateSignature()</strong> to validate an individual signature and <strong>document.form.validateSignatures()</strong> to validate all signatures in a PDF document.</p><h3>Conclusion</h3><p>Digital signatures help verify the authenticity and integrity of PDF documents, but trusted timestamps, Long-Term Validation (LTV), and signature validation are essential for maintaining trust over time.</p><p>In this blog, we explored how to sign PDFs in JavaScript, add trusted timestamps, enable LTV, and validate digital signatures using the Syncfusion <a href="https://www.syncfusion.com/document-sdk/javascript-pdf-library">JavaScript PDF Library</a>. By combining these capabilities, you can build secure PDF processes that remain verifiable long after documents are signed.</p><p>Ready to get started? Explore the Syncfusion JavaScript PDF Library and add <a href="https://help.syncfusion.com/document-processing/pdf/pdf-library/javascript/digitalsignature">digital signing and validation capabilities</a> to your applications.</p><p>If you’re an existing Syncfusion user, download the latest version from the <a href="https://www.syncfusion.com/account/downloads">license and downloads</a> page. New users can start with a <a href="https://www.syncfusion.com/downloads">free 30-day trial</a>.</p><p>For questions or assistance, reach out through the <a href="https://www.syncfusion.com/forums">support forum</a>, <a href="https://support.syncfusion.com/">support portal</a>, or <a href="https://www.syncfusion.com/feedback">feedback portal</a>.</p><h3>Related blogs</h3><p>· <a href="https://www.syncfusion.com/blogs/post/pades-digital-signature-dotnet"><strong>How to Implement PAdES Digital Signatures in .NET for Long-Term PDF Validation</strong></a></p><p>· <a href="https://www.syncfusion.com/blogs/post/add-in-app-digital-sign-wpf-pdf-viewer"><strong>Add Digital Signatures to a WPF PDF Viewer with a Click-to-Place eSign Workflow</strong></a></p><p>· <a href="https://www.syncfusion.com/blogs/post/syncfusion-pdf-library-vs-aspose-pdf"><strong>Syncfusion PDF Library vs Aspose.PDF: Comparing Features, Performance, and Accessibility</strong></a></p><p>· <a href="https://www.syncfusion.com/blogs/post/javascript-pdf-signature"><strong>How to Add and Customize Signature Blocks in PDFs Using JavaScript PDF Viewer</strong></a></p><p><em>Originally published at </em><a href="https://www.syncfusion.com/blogs/post/pdf-signature-validation-javascript"><em>https://www.syncfusion.com</em></a><em> on November 4, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e383eb157572" width="1" height="1" alt=""><hr><p><a href="https://medium.com/syncfusion/how-to-validate-pdf-digital-signatures-in-javascript-with-timestamps-and-long-term-validation-ltv-e383eb157572">How to Validate PDF Digital Signatures in JavaScript with Timestamps and Long-Term Validation (LTV)…</a> was originally published in <a href="https://medium.com/syncfusion">Syncfusion, Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Signs of Technical Debt in Vibe Coding and How to Refactor]]></title>
            <link>https://medium.com/syncfusion/7-signs-of-technical-debt-in-vibe-coding-and-how-to-refactor-d37244b69850?source=rss----f6ee85f5a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/d37244b69850</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[tips-and-tricks]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Rajeshwari Pandinagarajan]]></dc:creator>
            <pubDate>Fri, 06 Nov 2026 11:16:04 GMT</pubDate>
            <atom:updated>2026-11-06T11:16:04.468Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="7 Signs of Technical Debt in Vibe Coding and How to Refactor" src="https://cdn-images-1.medium.com/max/1024/0*3zfHzzBiKq0tIqBn.jpg" /></figure><blockquote><strong><em>TL;DR:</em></strong><em> </em>Vibe coding helps developers build features quickly, but repeated AI-generated changes can leave behind duplicated logic, inconsistent patterns, and code that is difficult to maintain. Learn seven warning signs of technical debt, how to audit a feature across its changes, and a practical approach for deciding what to refactor.</blockquote><h3>Introduction</h3><p>A developer asks an AI coding assistant to create a function. Another prompt adds validation, and a third handles an edge case. Within a short time, the feature is implemented, the code compiles, and the tests pass.</p><p>Everything appears to be working as expected. But then comes a small change.</p><p>You revisit the code and find duplicated logic, business rules scattered across files, and components with unnecessary dependencies. What seemed like a straightforward implementation has become more difficult to modify.</p><p>This is one of the challenges of AI-assisted development. When generated code is accepted without considering the overall application architecture, quick solutions can gradually introduce technical debt.</p><p>Let’s explore why this happens, how to identify the warning signs, and what developers can do to keep AI-generated code maintainable.</p><h3>What is Vibe Coding Technical Debt?</h3><p>Vibe coding is an informal way of building software through iterative conversations with AI. You describe what you want, an AI assistant generates or modifies code, and you refine the result through further prompts.</p><p>Technical debt refers to design or implementation decisions that make software harder or more expensive to maintain, extend, or modify later. A solution may work today but still make future changes more difficult. Technical debt is not necessarily a bug, although debt and defects can exist together.</p><p>AI-generated technical debt can be difficult to notice because the code may run and tests may pass, even when coverage is incomplete. An assistant may also suggest a solution that works for the immediate request but duplicates an existing implementation or conflicts with a project convention.</p><p>The important distinction is between a change that works for the current task and a change that fits the application as a whole.</p><h3>How it happens</h3><p>Imagine asking an AI assistant to add authentication to an endpoint. It adds a token check at the beginning of the function. The endpoint works.</p><p>The next week, you need rate limiting. Another conditional is added. Then, you request logging, guest-user handling, and an administrator exception.</p><p>After several changes, the endpoint may contain authentication, authorization, rate limiting, logging, and business logic in one function. Testing becomes more complicated, and each new change has more responsibilities to consider.</p><p>The pattern can spread across the application. Different endpoints may end up with slightly different authentication implementations, duplicated rate-limiting logic, and inconsistent administrator checks. Each change may work in isolation, while the accumulation makes the code harder to maintain.</p><h3>Before vs. After vs. Refactored</h3><p>Here’s a simplified JavaScript example of how an endpoint can become a patchwork of unrelated responsibilities.</p><h3>Before: Clean service function</h3><pre>async function getUserProfile(userId) {<br>  return await db.users.findById(userId);<br>}</pre><h3>After: Patchwork function</h3><pre>async function getUserProfile(userId, token, req) {<br>  if (!token) throw new Error(&#39;No token&#39;);<br><br>  // Decoding does not verify the token signature.<br>  const decoded = jwt.decode(token);<br>  if (!decoded) throw new Error(&#39;Invalid token&#39;);<br><br>  const isAdmin = await db.admins.exists(decoded.id);<br><br>  if (!isAdmin) {<br>    const recentCalls = await redis.get(`calls:${decoded.id}`);<br>    if (recentCalls &gt; 100) throw new Error(&#39;Rate limited&#39;);<br>  }<br><br>  logger.info(`Fetching profile for ${decoded.id}`);<br>  if (isAdmin &amp;&amp; req?.guestAccess) {<br>    // Special handling for guest administrators<br>  }<br><br>  return await db.users.findById(userId);<br>}</pre><p>This example intentionally shows responsibilities accumulating in one function. It is not a recommended authentication implementation. In particular, <strong>jwt.decode()</strong> only decodes a token; it does not verify its signature. Decoding alone must not be used to authenticate a request.</p><h3>After refactoring: Separate responsibilities</h3><pre>// Authentication middleware verifies the token.<br>function authMiddleware(req, res, next) {<br>  const token = req.headers.authorization?.replace(/^Bearer\s+/, &#39;&#39;);<br><br>  if (!token) {<br>    return res.status(401).json({ error: &#39;Authentication required&#39; });<br>  }<br><br>  try {<br>    req.user = jwt.verify(token, process.env.JWT_SECRET);<br>    return next();<br>  } catch {<br>    return res.status(401).json({ error: &#39;Invalid or expired token&#39; });<br>  }<br>}<br><br>// The service is configured separately from the route handler.<br>const rateLimiter = new RateLimitService();<br><br>// Rate limiting is handled separately.<br>async function rateLimitMiddleware(req, res, next) {<br>  try {<br>    const allowed = await rateLimiter.isAllowed(req.user.id);<br>    if (!allowed) {<br>      return res.status(429).json({ error: &#39;Rate limited&#39; });<br>    }<br>    return next();<br>  } catch (error) {<br>    return next(error);<br>  }<br>}<br><br>// The endpoint focuses on retrieving the signed-in user&#39;s profile.<br>async function getUserProfile(req, res, next) {<br>  try {<br>    const user = await db.users.findById(req.user.id);<br>    if (!user) {<br>      return res.status(404).json({ error: &#39;User not found&#39; });<br>    }<br>    logger.info(`Profile accessed by ${req.user.id}`);<br>    return res.json(user);<br>  } catch (error) {<br>    return next(error);<br>  }<br>}<br><br>// Example Express route; middleware order matters.<br>router.get(&#39;/profile&#39;, authMiddleware, rateLimitMiddleware, getUserProfile);</pre><p>This is an illustrative Express-style example. It assumes that the JWT secret, database, logger, and rate-limiter service are configured, and that the application has appropriate error-handling middleware. The route applies authentication before rate limiting and the endpoint. Applications that allow access to other users’ profiles also need an explicit authorization check.</p><p>The improvement is not simply fewer lines. Each part now has a clear responsibility, and the route makes the request flow visible. That makes the code easier to review and gives developers clearer places to test authentication, rate limiting, and profile retrieval independently.</p><h3>7 signs your vibe-coded project is becoming patchwork</h3><p>These signs are prompts for investigation, not a formal scoring standard. One sign alone doesn&#39;t prove a codebase has serious debt. Look for recurring patterns and their impact.</p><figure><img alt="Recurring patterns and their impact" src="https://cdn-images-1.medium.com/max/1024/1*78OvCwdOpRQPi5G6Pcrj5Q.png" /></figure><h3>1. You keep changing the same files</h3><p>Check your Git history. If the same files appear repeatedly in commits during a sprint, you may be patching symptoms instead of solving the underlying problem.</p><p><strong>What to do:</strong> Review the changes together. Are they all fixing different symptoms of the same design issue? Treat repeated changes as a signal to investigate, not as a fixed numerical threshold.</p><h3>2. The same logic exists in multiple places</h3><p>Authentication logic may appear separately in <strong>users.js</strong>, <strong>posts.js</strong>, and <strong>comments.js</strong>, with slightly different implementations. When the rule changes, every copy needs to be updated.</p><p><strong>What to do:</strong> Identify genuinely shared behavior and consider extracting it into middleware, a helper, or a service. Avoid creating an abstraction when the code only looks similar but serves different purposes.</p><h3>3. Conditionals keep growing</h3><p>Nested conditions can accumulate for administrators, moderators, premium users, guests, and other special cases. As the logic grows, it becomes harder to understand which rules apply and how they interact.</p><p><strong>What to do:</strong> Clarify the business rules first. Consider role-based access control (RBAC) when permissions are organized around roles, or a policy-based approach when access depends on more detailed conditions. Choose an approach that fits the application.</p><h3>4. Dependencies pile up</h3><p>An AI assistant may suggest a new library without knowing that the project already has a dependency for the same purpose. A codebase might gradually include multiple utility or date-handling libraries.</p><p><strong>What to do:</strong> Check whether an existing dependency or built-in capability already meets the requirement. Consider maintenance status, compatibility, security, and bundle-size impact where relevant before adding another package.</p><h3>5. Architecture is all over the place</h3><p>One part of an application may use MVC, another may use functional handlers, and another may introduce classes for similar responsibilities. Data access may also vary without a clear reason.</p><p><strong>What to do:</strong> Document the patterns the team wants to follow, including routing, data access, authentication, error handling, and testing. Share relevant guidance when prompting AI assistants.</p><h3>6. Tests get changed to make code pass</h3><p>Imagine a test expects verified to be true. It fails, and an AI assistant changes the expectation to false. The test now passes, but the implementation may still be wrong.</p><p><strong>What to do:</strong> Understand why the test failed before changing it. Fix the implementation when it does not meet the requirement. Change a test when expected behavior has genuinely changed, not just to make a failing test pass.</p><h3>7. Nobody knows why code exists</h3><p>Comments such as “Not sure if needed” or “Don’t remove, breaks prod” are warning signs when they do not explain the reason behind the code.</p><p><strong>What to do:</strong> Trace the code to the requirement or decision that introduced it. Document important constraints and why a particular approach was chosen. Confirm that code is no longer needed before removing it.</p><h3>A practical audit: Follow one feature across its changes</h3><p>A useful way to find AI-related technical debt is to audit one feature rather than asking an assistant to review the entire repository and accepting a long list of generic suggestions.</p><p>For example, choose the profile endpoint from the earlier code sample. Review the feature in this order:</p><ol><li><strong>Trace the change history:</strong> Use <strong>git log --oneline -- path/to/profile-file.js</strong> to see commits that changed the file. Open the relevant diffs and identify which requirements led to each change.</li><li><strong>Map the responsibilities:</strong> List what the endpoint currently handles: token validation, permission checks, rate limiting, logging, database access, and response formatting.</li><li><strong>Find duplicated behavior:</strong> Search for other endpoints that implement the same authentication or rate-limiting rules. Compare the behavior, not just the names of the functions.</li><li><strong>Check the tests:</strong> Find tests for valid tokens, missing or invalid tokens, rate limits, missing users, and unexpected database errors. Confirm that the tests reflect the intended behavior.</li><li><strong>Review dependencies and assumptions:</strong> Check whether the endpoint uses existing project services and conventions. Identify any new package or special-case rule that needs justification.</li><li><strong>Record findings before changing code:</strong> Separate confirmed defects from maintainability concerns and possible improvements.</li></ol><p>A simple audit note could look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KheD5pzbKc6Hv1zzzd8-Wg.png" /></figure><p>This is where the audit becomes more valuable than a generic code review: every finding is tied to a specific file, behavior, or requirement. Do not refactor solely because an AI tool labels something as complex. First confirm that the issue exists and that the proposed change preserves the required behavior.</p><h3>Why AI-assisted development can accumulate debt</h3><p>AI coding assistants can generate useful local changes, but they may not always account for the whole system. Several factors contribute to this risk:</p><ul><li><strong>Incomplete context:</strong> An assistant may not have access to every relevant file, architectural decision, or business rule. Even when it can inspect a repository, it may not understand why an existing pattern was chosen.</li><li><strong>Local task focus:</strong> A generated change may address the prompt without considering every system-wide effect. Developers still need to review maintainability, consistency, and integration.</li><li><strong>Limited continuity:</strong> Context can vary by tool, configuration, and session. Without project-level guidance, later suggestions may not follow earlier decisions.</li><li><strong>Patches hide root causes:</strong> When a patch fixes an immediate symptom, the underlying design issue may remain.</li><li><strong>Fast iteration:</strong> AI makes code generation faster. If review and refactoring do not receive enough attention, changes can accumulate faster than the team can evaluate them.</li></ul><p>The lesson is not that AI-generated code is inherently worse than human-written code. Both need review. The important question is whether each change meets the same standards for correctness, security, consistency, and maintainability.</p><h3>A six-step approach to stop the patchwork</h3><p>Use this approach when a change touches an area that has become difficult to maintain.</p><h4>Step 1: PAUSE</h4><p>Stop coding and step back. Ask yourself:</p><ul><li>Am I solving the right problem?</li><li>Is this a band-aid for a bigger issue?</li><li>Have I changed this area repeatedly?</li><li>Did the AI assistant have the architectural context needed for this change?</li></ul><h4>Step 2: INSPECT</h4><p>Open your Git diff and review the recent history of the files you changed. Then ask:</p><ul><li>Do I understand every important line that was added?</li><li>Is the change consistent with the rest of the codebase?</li><li>Would I approve this implementation in a code review?</li><li>Does it solve the underlying problem or only address a symptom?</li></ul><h4>Step 3: TEST</h4><p>Check whether tests cover the changed behavior:</p><ul><li>What about edge cases?</li><li>Does error handling work as expected?</li><li>What happens with missing, invalid, or unexpected input?</li><li>Could this change affect another part of the application?</li></ul><p>You can ask AI to suggest missing test cases, but review those suggestions against the actual requirements. Tests should verify expected behavior, not simply make the implementation pass.</p><h4>Step 4: REFACTOR</h4><p>Improve the structure where necessary:</p><ul><li>Pull genuinely duplicated code into shared functions.</li><li>Simplify deeply nested conditionals.</li><li>Group related responsibilities together.</li><li>Simplify unnecessarily complex function signatures.</li><li>Remove unused code or dependencies only after confirming they are not needed.</li><li>Add comments that explain important decisions.</li></ul><p>Ask AI to suggest a behavior-preserving refactor and explain the proposed changes. Review the result and run relevant tests before accepting it.</p><h4>Step 5: DOCUMENT</h4><p>Write down why a decision was made, not just what the code does. For example, explain why the team chose a simple discount implementation instead of introducing a rule-engine library, and what future change would justify revisiting that decision.</p><h4>Step 6: CONTINUE</h4><p>Once the change is reviewed, tested, and easier to maintain, continue building. The goal is to address complexity before it becomes expensive to manage.</p><h3>Should you patch, refactor, or rebuild?</h3><p>Not every issue needs a large refactor. Choose the smallest change that safely addresses the underlying problem.</p><figure><img alt="Comparing patch, refactor and build" src="https://cdn-images-1.medium.com/max/1024/1*fKo_fCbXyuzZLNthKFAYwA.png" /></figure><p>A rebuild should not be the automatic response to a messy codebase. It can introduce new risks and may recreate the same problems if the underlying requirements and design decisions are not addressed. Prefer incremental refactoring when it can safely improve the system.</p><h3>Team practices for AI-assisted development</h3><p>Technical debt is also a team concern. Shared practices help keep generated code consistent:</p><ul><li><strong>Share architecture guidance:</strong> Document the project’s routing, data access, authentication, error-handling, and testing conventions.</li><li><strong>Maintain reviewed prompts:</strong> Keep useful prompts for common tasks, but update them when project patterns change.</li><li><strong>Review high-impact changes carefully:</strong> Give additional attention to authentication, authorization, data access, and new dependencies.</li><li><strong>Use AI as a review aid:</strong> Ask it to identify edge cases, duplication, and possible inconsistencies. Developers remain responsible for verifying the findings.</li></ul><h3>Quick audit checklist</h3><p>Use these questions during a code review or maintenance session:</p><ul><li>Is the same logic implemented in multiple files?</li><li>Are some files repeatedly changed to address related issues?</li><li>Are there several different ways to handle the same operation, such as authentication, logging, or validation?</li><li>Are multiple libraries being used for essentially the same purpose?</li><li>Is important conditional logic deeply nested or difficult to follow?</li><li>Are there comments such as “Don’t touch this” without an explanation?</li><li>Does the team struggle to explain why an important piece of code exists?</li></ul><p>Use the answers to identify areas for investigation, not to produce a formal technical-debt score. Prioritize findings by their impact on security, correctness, maintainability, and the effort required to fix them.</p><h3>AI prompt template: Architecture-first approach</h3><p>Use this template to give an AI assistant context before asking it to implement a change.</p><pre>TASK: [Describe what you want to build or change.] <br><br>PROJECT CONTEXT: <br>[Relevant files, architecture, existing patterns, and constraints.] <br><br>PATTERNS: <br>[Authentication, logging, data access, error handling, and testing conventions.] <br><br>CONSTRAINTS: <br>- Reuse existing abstractions where appropriate. <br>- Avoid unnecessary dependencies. <br>- Preserve existing behavior unless requirements say otherwise. <br>- Include relevant tests. <br>- Explain assumptions and trade-offs. <br><br>BEFORE IMPLEMENTING: <br><br>1. Identify relevant existing code. <br>2. Explain which patterns or abstractions can be reused. <br>3. Identify possible edge cases and risks. <br>4. Present an implementation plan. <br><br>THEN: <br>Implement the approved approach and summarize the changes and tests.</pre><p>Review the proposed plan and generated code before using them. Providing context improves the quality of the discussion, but it does not guarantee that generated code is correct.</p><h3>Frequently Asked Questions</h3><p><strong>1. What if my codebase is already a patchwork? Is it too late to fix?</strong></p><p>No. Start with the file or feature causing the most maintenance problems. Review its behavior, add or improve tests, extract duplicated logic where appropriate, and clarify its responsibilities. Work in manageable steps rather than trying to restructure the entire application at once.</p><p><strong>2. Are there situations where quick AI patches are fine?</strong></p><p>Yes. Quick patches can be appropriate for prototypes, throwaway experiments, or low-risk changes when the trade-offs are understood. Before a prototype becomes production code, review its architecture, security, and test coverage.</p><p><strong>3. How do I convince my team to make time for refactoring?</strong></p><p>Track examples of repeated bug fixes, slow code reviews, and time spent understanding complex areas. Explain how addressing a specific source of complexity could reduce future maintenance effort. Start with a focused improvement and use the result to demonstrate its value.</p><p><strong>4. Does using AI automatically create technical debt?</strong></p><p>No. AI-generated code can be maintainable when it is reviewed, tested, and aligned with the project’s requirements and architecture. Technical debt can result from human-written code as well. The important factor is how changes are evaluated and maintained.</p><h3>Keep the speed, lose the patchwork</h3><p>Vibe coding is not inherently flawed. AI assistants can help developers explore ideas and build features faster. Problems arise when rapid iteration happens without enough attention to architecture, testing, and maintainability.</p><p>The seven warning signs help identify a codebase that is becoming harder to change. The practical audit shows how to trace a concern back to specific code and supporting evidence. The six-step approach helps developers inspect, test, refactor, and document changes, while the patch-or-refactor guide helps determine the right level of response.</p><p>Start with one feature or file that repeatedly causes maintenance work. Trace its history, verify the behavior, and prioritize the issues that have the greatest impact. Use AI to analyze and review code, but keep developers responsible for understanding and approving the changes.</p><p>Build faster with AI while keeping your codebase maintainable.</p><h3>Related blogs</h3><p>· <a href="https://www.syncfusion.com/blogs/post/jev-ai-vs-structured-output-llms">Jev AI vs. Structured-Output LLMs: Which One Should You Actually Use?</a></p><p>· <a href="https://www.syncfusion.com/blogs/post/rag-vs-fine-tuning-in-gpt-approach">RAG vs Fine-Tuning: Most Teams Get This Wrong (Here’s the Fix)</a></p><p>· <a href="https://www.syncfusion.com/blogs/post/context-engineering-smart-ai-prompts">Context Engineering: Improving AI Code Output in Your IDE</a></p><p>· <a href="https://www.syncfusion.com/blogs/post/prompt-engineering-vibe-coding">Prompt Engineering + Vibe Coding: A New Era for Software Developers</a></p><p><em>Originally published at </em><a href="https://dev.to/syncfusion/7-signs-of-technical-debt-in-vibe-coding-and-how-to-refactor-348n"><em>https://dev.to</em></a><em> on November 6, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d37244b69850" width="1" height="1" alt=""><hr><p><a href="https://medium.com/syncfusion/7-signs-of-technical-debt-in-vibe-coding-and-how-to-refactor-d37244b69850">7 Signs of Technical Debt in Vibe Coding and How to Refactor</a> was originally published in <a href="https://medium.com/syncfusion">Syncfusion, Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jev AI vs. Structured-Output LLMs: Which One Should You Actually Use?]]></title>
            <link>https://medium.com/syncfusion/jev-ai-vs-structured-output-llms-which-one-should-you-actually-use-901590a963db?source=rss----f6ee85f5a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/901590a963db</guid>
            <category><![CDATA[large-language-models]]></category>
            <category><![CDATA[structured-output]]></category>
            <category><![CDATA[ai-architecture]]></category>
            <category><![CDATA[ai-decision-model]]></category>
            <category><![CDATA[jevai]]></category>
            <dc:creator><![CDATA[Rajeshwari Pandinagarajan]]></dc:creator>
            <pubDate>Tue, 03 Nov 2026 09:48:17 GMT</pubDate>
            <atom:updated>2026-11-03T09:48:17.401Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Jev AI vs. Structured-Output LLMs: Which One Should You Actually Use?" src="https://cdn-images-1.medium.com/max/1024/1*bRVkcyoogFljTSdHyBC1UA.jpeg" /></figure><blockquote><strong>TL;DR:</strong> Choosing between Jev AI and structured-output LLMs? It comes down to the task. Jev AI is great for quick decisions like categorizing, scoring, and routing, while structured-output LLMs handle tasks like extracting data, explaining results, and planning. Need both? You can combine them. Just remember: well-formatted output doesn’t always mean a correct decision. Test with your own data, and keep critical business rules in your application code.</blockquote><p>Imagine a customer submits a support ticket saying they’re locked out of their account. Your AI model reads the ticket, returns perfectly formatted JSON, and routes the issue to the billing team instead of security.</p><p>Here’s an example response:</p><pre>{<br>  &quot;route&quot;: &quot;billing&quot;,<br>  &quot;priority&quot;: &quot;low&quot;,<br>  &quot;requires_human_review&quot;: false<br>}</pre><p>The format is flawless. The decision is wrong.</p><p>That’s the problem in a nutshell. A model can return an answer that passes every structural check and still misunderstand the actual situation.</p><p>There are two approaches worth considering:</p><ul><li><strong>Structured-output LLMs</strong>: Constrain a model’s response to a format or schema you define.</li><li><strong>Typed decision models like Jev AI</strong>: Return clear, bounded answers, such as a category, score, or yes/no probability.</li></ul><p>In this guide, we’ll explore how each approach works, when to use it, how to test it, and where document data fits into the process.</p><blockquote><strong>A note on sources</strong>: Information about Jev AI and its maker, TypeSafe, in this article is based on their published documentation at the time of writing. Treat any performance, speed, cost, or capability claims as the provider’s reported figures until you’ve tested them with your own data. Always check the official TypeSafe <a href="https://docs.typesafe.ai/introduction/quickstart">Quick Start</a> and <a href="https://docs.typesafe.ai/api/system-one">API Reference</a> for the latest request and response formats before implementation.</blockquote><h3>How we used to handle messy model output</h3><p>For a long time, working with LLM output involved the same repetitive process: write detailed prompt instructions, parse the JSON, validate it, and retry whenever the response broke the expected format.</p><p>Then providers such as OpenAI and Anthropic introduced structured-output features. These allow developers to constrain a model’s response to a predefined schema. That’s a significant improvement, although the exact rules and capabilities vary by provider and API version.</p><p>Structured output helps address several common problems:</p><ul><li>Required fields must be present.</li><li>Field types remain consistent.</li><li>Dropdown-style values stay within the allowed options.</li><li>Tool inputs match their definitions.</li><li>Your application code spends less time handling malformed JSON.</li></ul><p>However, structured output doesn’t guarantee that the answer is correct. It controls the shape of the response, not the accuracy of the model’s judgment.</p><h3>Structured outputs in 60 seconds</h3><p>A structured-output LLM is a regular text-generating model configured to return its response in a format you define.</p><p>For example, you might define a TypeScript type for assessing support tickets:</p><pre>type TicketAssessment = {<br>  summary: string;<br>  route: &quot;billing&quot; | &quot;technical&quot; | &quot;account&quot;;<br>  urgency: number;<br>  explanation: string;<br>};</pre><p>This approach is useful when a task requires more than a simple decision, such as:</p><ul><li>Extracting multiple fields from a contract.</li><li>Writing an explanation for a human reviewer.</li><li>Summarizing an incident before categorizing it.</li><li>Creating a step-by-step plan.</li><li>Converting a conversation into tool inputs.</li><li>Returning supporting quotes or evidence alongside an answer.</li></ul><p>The biggest advantage is flexibility. One model can interpret instructions, summarize information, generate text, call tools, and populate structured data.</p><p>The limitation is that matching a schema doesn’t prove the content is accurate or that the model’s confidence is reliable. For example, a field such as “confidence”: 0.93 is just a number generated by the model until you’ve tested how often its predictions are actually correct.</p><h3>So, what is Jev AI?</h3><p>Jev AI is TypeSafe’s flagship <a href="https://docs.typesafe.ai/concepts/system-one">System One</a> model. The name reflects its focus: quick, bounded judgments rather than lengthy reasoning or essay writing.</p><p>Instead of returning paragraphs, Jev AI provides clear, typed answers.</p><p>You send Jev two things:</p><ul><li><a href="https://docs.typesafe.ai/concepts/state"><strong>State</strong></a>: The information it needs to evaluate, such as a support ticket, transaction, policy, or application data.</li><li><strong>Typed questions</strong>: The specific decisions you want it to make.</li></ul><p>Jev AI returns answers through three main building blocks:</p><ul><li><a href="https://docs.typesafe.ai/primitives/choice"><strong>Choice</strong></a>: Selects one option from a list you define and provides the probability for each option, along with a confidence value.</li><li><a href="https://docs.typesafe.ai/primitives/score"><strong>Score</strong></a>: Evaluates a situation against levels you define and returns a score, the probability for each level, and a confidence value.</li><li><a href="https://docs.typesafe.ai/primitives/noul"><strong>Noul</strong></a>: Answers a single yes/no question and provides the probability that the answer is yes.</li></ul><p>There’s also an experimental <strong>Box</strong> building block for image-related tasks. However, TypeSafe identifies it as a feature that is still changing, so avoid depending on it for critical workflows until its behavior is established. Always confirm these definitions in the current documentation.</p><p>The key is to break a large decision into smaller, specific questions.</p><p>Instead of asking a model, “Look at this ticket and decide what to do,” you could ask:</p><ul><li><strong>Choice</strong>: Which team should handle this ticket?</li><li><strong>Score</strong>: How seriously is the customer affected?</li><li><strong>Noul</strong>: Does this situation require immediate human review?</li></ul><p>Your application code then uses those answers alongside business rules and authoritative account data to make the final decision.</p><h3>Jev AI vs. Structured-Output LLMs: A side-by-side comparison</h3><p>Capabilities vary by provider, model, and version. Use this comparison as a general guide rather than a guarantee about every available tool.</p><h3>Understanding Jev AI’s confidence values</h3><p>For <strong>Choice</strong> and <strong>Score</strong>, Jev AI provides a confidence value between 0 and 1. This value reflects how clearly the probabilities point toward one outcome.</p><p>If one option clearly stands out, confidence is high. If the probabilities are close, confidence is low.</p><p><strong>Noul</strong> doesn’t provide a separate confidence field. Its output is the probability that the yes/no statement is true.</p><p>In either case, test these values against your own labeled data before relying on them.</p><h3>A bounded answer can still be wrong</h3><p>Suppose a <strong>Choice</strong> question allows only four options: billing, technical, security, and other.</p><p>Jev AI can’t return a fifth option outside that list. However, it can still select billing for a ticket that describes a security problem.</p><p>Staying within the allowed options doesn’t mean the selected option is correct.</p><h3>Which one should you choose?</h3><p>Here’s a simple way to decide:</p><ul><li>Need text generation, data extraction, or planning? Use a <strong>structured-output LLM</strong>.</li><li>Need a clear, bounded decision? Try <strong>Jev AI</strong>.</li><li>Need to generate data and make decisions about it? Use <strong>both together</strong>.</li><li>Have a non-negotiable rule? Keep it in <strong>application code</strong>, not in a model.</li></ul><h3>First, where does the data come from?</h3><p>Here’s something that’s easy to overlook: both approaches depend on the quality of the data you provide.</p><p>Feed a model incomplete or incorrect information, and you can get confident, well-formatted but equally incorrect results.</p><p>In most business applications, that information starts in documents. These might include PDFs, Word files, Excel spreadsheets, scanned images, or email attachments.</p><p>Converting these files into clean, usable data is a document-processing task. That’s where the Syncfusion® <a href="https://www.syncfusion.com/document-sdk">Document SDK</a> can help:</p><ul><li><a href="https://www.syncfusion.com/document-sdk/net-pdf-library"><strong>PDF Library</strong></a>: Extract text and form data from PDF documents.</li><li><a href="https://www.syncfusion.com/document-sdk/net-word-library"><strong>Word Library (DocIO)</strong></a>: Extract clauses, headings, and fields from Word documents.</li><li><a href="https://www.syncfusion.com/document-sdk/net-excel-library"><strong>Excel Library (XlsIO)</strong></a>: Extract line items and totals from spreadsheets.</li><li><a href="https://www.syncfusion.com/document-sdk/net-pdf-library/ocr-process"><strong>OCR processor</strong></a>: Convert scanned or image-based documents into readable text.</li></ul><h3>A typical document-to-AI pipeline</h3><p>A real-world pipeline might look like this:</p><ul><li><strong>Extract document content</strong>: Use Syncfusion® <a href="https://www.syncfusion.com/document-sdk">Document SDK</a> to retrieve content from the source file without involving an AI model.</li><li><strong>Structure the data</strong>: Use a structured-output LLM to organize the extracted content into fields such as names, dates, and line items.</li><li><strong>Make bounded decisions</strong>: Use Jev AI to answer specific questions about the structured data, such as which queue should handle it, how serious a mismatch is, or whether it should be escalated.</li><li><strong>Apply application rules</strong>: Use your code to enforce non-negotiable rules and validate decisions against authoritative data.</li></ul><p>The benefit is straightforward: reliable document processing gives your AI layer cleaner input. This also helps ensure your tests measure the model’s performance rather than errors introduced during document parsing.</p><p>Explore the Syncfusion <a href="https://help.syncfusion.com/document-processing/introduction">Document SDK documentation</a> and samples to find the formats and APIs that fit your platform.</p><h3>A smart way to connect everything</h3><p>The golden rule is simple: keep model judgments separate from hard rules.</p><p>Security, authentication, permissions, compliance, and validation rules should run independently. A model must never be allowed to override them.</p><p>Here’s the workflow:</p><ul><li>Start with a document source, such as a PDF, Word document, Excel spreadsheet, or scanned file.</li><li>Use the Syncfusion® <a href="https://www.syncfusion.com/document-sdk">Document SDK</a> to extract the content and convert it into application data (state).</li><li>Send that state through two separate paths:</li></ul><p>— <strong>Path 1 — Hard rules</strong>: Apply security, authentication, and compliance checks to determine the enforced outcome.</p><p>— <strong>Path 2 — Model judgments</strong>: Use Jev AI or a structured-output LLM, then validate the results against your checks and risk thresholds.</p><ul><li>Automate the action when the result is sufficiently reliable and low risk.</li><li>Send uncertain or high-risk results to a human reviewer.</li></ul><h3>Example: Enforcing a Security Policy Before Routing a Ticket</h3><p>The following example illustrates how application code can enforce a mandatory security rule before using model-generated decisions.</p><p><strong>Important</strong>: This is a conceptual example, not production-ready SDK code. It is not a real Jev integration, and TicketDecision is not a real Jev type. A production implementation would also need to handle authentication errors, timeouts, rate limits, and unexpected responses. Refer to the official TypeSafe documentation for the actual request and response formats.</p><pre>type Department = &quot;billing&quot; | &quot;technical&quot; | &quot;security&quot; | &quot;other&quot;;<br><br>type TicketState = {<br>  suspectedAccountCompromise: boolean;<br>};<br><br>type TicketDecision = {<br>  department?: { choice?: unknown; confidence?: number };<br>  immediateEscalation?: { noul?: number };<br>  impact?: { score?: number; confidence?: number };<br>};<br><br>type NextStep =<br>  | { action: &quot;security_review&quot;; reason: &quot;mandatory_security_policy&quot; }<br>  | { action: &quot;human_review&quot;; reason: string }<br>  | { action: &quot;auto_route&quot;; team: Department };<br><br>const departments = [&quot;billing&quot;, &quot;technical&quot;, &quot;security&quot;, &quot;other&quot;] as const;<br><br>function isDepartment(value: unknown): value is Department {<br>  return (<br>    typeof value === &quot;string&quot; &amp;&amp;<br>    (departments as readonly string[]).includes(value)<br>  );<br>}<br><br>const inUnitInterval = (value: unknown): value is number =&gt;<br>  typeof value === &quot;number&quot; &amp;&amp; Number.isFinite(value) &amp;&amp; value &gt;= 0 &amp;&amp; value &lt;= 1;<br><br>const inImpactRange = (value: unknown): value is number =&gt;<br>  typeof value === &quot;number&quot; &amp;&amp; Number.isFinite(value) &amp;&amp; value &gt;= 0 &amp;&amp; value &lt;= 3;<br><br>function chooseNextStep(state: TicketState, result: TicketDecision): NextStep {<br>  // Hard rule always wins, no matter what the model says.<br>  if (state.suspectedAccountCompromise) {<br>    return { action: &quot;security_review&quot;, reason: &quot;mandatory_security_policy&quot; };<br>  }<br><br>  const department = result.department;<br>  const immediateEscalationProbability = result.immediateEscalation?.noul;<br>  const impact = result.impact;<br><br>  const valid =<br>    department !== undefined &amp;&amp;<br>    isDepartment(department.choice) &amp;&amp;<br>    inUnitInterval(department.confidence) &amp;&amp;<br>    inUnitInterval(immediateEscalationProbability) &amp;&amp;<br>    impact !== undefined &amp;&amp;<br>    inImpactRange(impact.score) &amp;&amp;<br>    inUnitInterval(impact.confidence);<br><br>  if (!valid) {<br>    return { action: &quot;human_review&quot;, reason: &quot;invalid_or_missing_model_output&quot; };<br>  }<br><br>  const sensitiveRoute = department.choice === &quot;security&quot; || impact.score &gt;= 2.5;<br>  const uncertain = department.confidence &lt; 0.85 || impact.confidence &lt; 0.8;<br><br>  if (sensitiveRoute || uncertain || immediateEscalationProbability &gt; 0.75) {<br>    return { action: &quot;human_review&quot;, reason: &quot;risk_or_uncertainty_threshold&quot; };<br>  }<br><br>  return { action: &quot;auto_route&quot;, team: department.choice };<br>}</pre><h3>Understanding the impact scale</h3><p>The example uses the following impact levels:</p><ul><li><strong>0</strong>: Nobody notices.</li><li><strong>1</strong>: Minor issue, with a workaround available.</li><li><strong>2</strong>: Something important is broken for one or more users.</li><li><strong>3</strong>: A major outage, security exposure, or similar issue.</li></ul><p>The thresholds in the example, 2.5, 0.85, 0.80, and 0.75, are illustrative values, not recommended defaults.</p><p>Choose your own thresholds using real labeled data. Consider the cost of an incorrect decision, your team’s review capacity, and how easily an action can be reversed.</p><p>The <strong>Noul</strong> question in this example is: “Does this ticket need a human right away?”</p><p>Define exactly what that question means before allowing its probability to influence an application action.</p><h3>Where can you use these approaches?</h3><p>Here are three practical scenarios where Jev AI and structured-output LLMs can work together.</p><h3>1. Support and incident triage</h3><p>Jev AI is useful when you repeatedly need to route support tickets to teams, score their impact, or identify possible escalations.</p><p>A structured-output LLM is a better fit when you also need to summarize a ticket, extract reproduction steps, or draft a response.</p><p>Known account-compromise signals should always follow the mandatory security path. Jev AI can help assess less obvious cases, but it should never override that rule.</p><h3>2. AI-Agent guardrails</h3><p>Before an AI agent issues a refund, changes permissions, or deploys an application, a typed decision model can provide a risk signal.</p><p>However, authentication, permission checks, limits, and audit logging remain the responsibility of your application.</p><h3>3. Document processing</h3><p>Structured-output LLMs are generally better suited to extracting names, dates, clauses, and line items from documents. This can happen after a Syncfusion® <a href="https://www.syncfusion.com/document-sdk">Document SDK</a> has already converted the source file into clean text.</p><p>Jev AI can then evaluate the extracted information and make bounded decisions. For example, it can assign a review queue, score the seriousness of a mismatch, or assess whether enough evidence exists to automate a step.</p><p>In this workflow, one model turns content into structured data, while the other makes bounded decisions about that data.</p><p>Both approaches still need validation against your actual records.</p><h3>How to test it properly (don’t skip this)</h3><p>Before using either approach in a real workflow, you need to understand how reliably it performs.</p><p>First, let’s clarify one important term: calibration.</p><p>Calibration measures whether a model’s confidence matches reality. For example, if a model says it is 90% confident across a group of predictions, it should be correct about 90% of the time for that group to be well calibrated.</p><p>If the confidence doesn’t match actual results, you shouldn’t rely on that number to make decisions.</p><h3>Start with a labeled test set</h3><p>Choose one workflow that is easy to reverse. Before connecting the model to a real action, build a labeled test set.</p><p>Include:</p><ul><li>Normal, straightforward cases.</li><li>Ambiguous cases.</li><li>Cases with missing information.</li><li>Unusually worded or misleading cases.</li><li>Rare but high-impact scenarios.</li></ul><p>Also, keep the following points in mind:</p><ul><li><strong>For Choice</strong>: Add an other or needs_review option unless your list of choices is genuinely complete.</li><li><strong>For Score</strong>: Define each level using observable criteria.</li><li><strong>For Noul</strong>: Ask one question at a time so the response remains clear.</li></ul><h3>A practical testing checklist</h3><p>Once your test set is ready, follow these steps:</p><ul><li>Ask domain experts to define the correct answers and resolve disagreements.</li><li>Build a confusion matrix to identify which categories are being mixed up.</li><li>Measure precision and recall for each category instead of relying only on overall accuracy.</li><li>Test calibration by grouping predictions and comparing their confidence with actual outcomes.</li><li>Set thresholds based on risk, review capacity, and the cost of mistakes.</li><li>Run the new approach in shadow mode, where it observes cases without taking action.</li><li>Track speed (P50, P95, and P99), cost per decision, escalation frequency, and changes in the input data over time.</li></ul><h3>A quick example: Measuring security recall</h3><p>Suppose you test 100 confirmed security incidents.</p><p>The system correctly routes 92 incidents to security and misses eight. That gives you 92% recall for security on this test set.</p><p>That’s useful information, but it doesn’t tell you how often the system incorrectly routes non-security tickets to the security team.</p><p>To measure that, calculate precision using the false positives across your full test set. Then validate both precision and recall using fresh holdout data before moving to production.</p><h3>Roll out gradually and monitor results</h3><p>Once shadow testing produces acceptable results, roll out the workflow gradually. Define your rollback conditions before enabling live actions.</p><p>Consider rolling back if:</p><ul><li>Security recall drops.</li><li>Confidence calibration changes significantly.</li><li>Human review volume increases unexpectedly.</li><li>Response times become too slow.</li><li>The cost of correcting mistakes becomes too high.</li></ul><p>One more recommendation: pin the model version whenever possible.</p><p>If the provider uses a moving model label, record the label, date, questions, evaluation criteria, and test results. Repeat your tests whenever the provider changes the model or its behavior.</p><p>Finally, treat any speed or cost figures published by TypeSafe as provider-reported results until you reproduce them using your own data, traffic, and review process.</p><h3>Still not sure? Follow this decision flow</h3><p>Use these questions to choose the right approach:</p><ul><li>Need generated text, data extraction, or variable-length output? Use a <strong>structured-output LLM</strong>.</li><li>Can the task be expressed as a choice, score, or yes/no question? Try a <strong>typed decision model like Jev AI</strong>.</li><li>Does the task fit neither approach? Rework it or handle it in plain application code.</li><li>Need to generate data and make decisions about it? Use <strong>both approaches together</strong>.</li><li>Is the requirement a non-negotiable rule involving security, authentication, or compliance? Enforce it in <strong>application code</strong>, never in a model.</li></ul><h3>Quick glossary</h3><ul><li><strong>System One model</strong>: A model designed for fast, bounded decisions rather than deep reasoning.</li><li><strong>Noul</strong>: A Jev AI building block that returns the probability that a yes/no statement is true.</li><li><strong>Calibration</strong>: A measure of whether a model’s confidence matches how often it is correct.</li><li><strong>Constrained decoding</strong>: A technique that constrains a model’s output to a defined structure.</li><li><strong>Semantic correctness</strong>: Whether an answer is actually correct, rather than simply well-formatted.</li></ul><h3>Frequently Asked Questions</h3><ol><li><strong>What can I feed Jev AI?<br></strong>According to TypeSafe’s documentation, Jev AI accepts text in the form of a string, JSON object, or array of text values. It doesn’t directly accept audio or video.<br>Convert those inputs into text first. A document SDK can help process supported files, but you should still validate the converted content before relying on the resulting decision.</li><li><strong>Can I use Jev AI for regulated decisions?<br></strong>Jev AI can assist with regulated workflows, but a probability alone may not satisfy requirements involving explanations, fairness, or auditing.<br>Keep records of the input, questions, model version, probabilities, final outcome, and any human overrides. Obtain legal and compliance approval before automating high-impact decisions.</li><li><strong>What if Jev AI needs information that isn’t in the data I sent?<br></strong>A well-structured answer doesn’t prove that the input data is complete.<br>Retrieve authoritative information before making the decision, identify missing values clearly, and provide an unknown or human-review path wherever missing information could affect the outcome.</li><li><strong>If I use Jev AI, do I still need structured-output LLMs?<br></strong>Usually, yes.<br>Many real-world implementations use a structured-output LLM, together with a document SDK, to prepare the data. A typed decision model can then evaluate that data.<br>They work better as complementary tools than as competing alternatives.</li></ol><h3>Wrapping up</h3><p>Think of Jev AI as a specialist for small, clearly defined decisions such as sorting, scoring, and routing. Structured-output LLMs are generalists that handle tasks such as extracting information, explaining results, planning, and generating text.</p><p>Many applications can benefit from using both. Keep non-negotiable rules in your application code, and use a reliable document-processing layer to provide clean input data.</p><p>Start with one workflow that you can easily reverse. Evaluate accuracy, precision and recall for each category, calibration, speed, escalation rate, and cost using real data.</p><p>Only after those results meet your requirements should you allow a model to influence a live action.</p><h3>Where to go next</h3><ul><li>Review the current Jev AI building blocks and supported formats in the official TypeSafe Quick Start and API Reference.</li><li>Explore the Syncfusion <a href="https://help.syncfusion.com/document-processing/introduction">Document SDK documentation</a> to learn how to convert PDFs, Word documents, Excel spreadsheets, and scanned files into usable data for your AI workflows.</li><li>Try an extract-then-decide pipeline using one of your own documents.</li><li>Start a <a href="https://www.syncfusion.com/downloads/document-sdk?tag=es-seo-document-sdk-download-trial">free Syncfusion trial</a> and evaluate the Document SDKs in your application.</li></ul><h3>Related Blogs</h3><ul><li><a href="https://www.syncfusion.com/blogs/post/multi-agent-ai-systems-code-governance">Multi-Agent AI Systems: A Smarter Way to Detect and Manage Technical Debt</a></li><li><a href="https://www.syncfusion.com/blogs/post/ai-coding-assistant-agent-skills-mcp">Build Faster with Syncfusion AI Coding Assistant Tools: Agent Skills and MCP Servers</a></li><li><a href="https://www.syncfusion.com/blogs/post/ai-guardrails-coding-agents">Why AI Coding Agents Go Off Scope and How Guardrails Fix It</a></li><li><a href="https://www.syncfusion.com/blogs/post/ai-ide-evaluation-guide">How to Evaluate an AI IDE in 2026: Features That Matter for Development Teams</a></li></ul><p><em>Originally published at </em><a href="https://www.syncfusion.com/blogs/post/jev-ai-vs-structured-output-llms"><em>https://www.syncfusion.com</em></a><em> on November 2, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=901590a963db" width="1" height="1" alt=""><hr><p><a href="https://medium.com/syncfusion/jev-ai-vs-structured-output-llms-which-one-should-you-actually-use-901590a963db">Jev AI vs. Structured-Output LLMs: Which One Should You Actually Use?</a> was originally published in <a href="https://medium.com/syncfusion">Syncfusion, Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Compare PDF Documents in JavaScript Using Syncfusion PDF Viewer]]></title>
            <link>https://medium.com/syncfusion/how-to-compare-pdf-documents-in-javascript-using-syncfusion-pdf-viewer-85c90843826c?source=rss----f6ee85f5a2---4</link>
            <guid isPermaLink="false">https://medium.com/p/85c90843826c</guid>
            <category><![CDATA[pdf]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[document-processing]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[pdf-viewer]]></category>
            <dc:creator><![CDATA[Rajeshwari Pandinagarajan]]></dc:creator>
            <pubDate>Mon, 02 Nov 2026 11:36:57 GMT</pubDate>
            <atom:updated>2026-11-02T11:36:57.450Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="How to Compare PDF Documents in JavaScript Using Syncfusion PDF Viewer" src="https://cdn-images-1.medium.com/max/1024/0*ZZfk-Z7KVg91SmEf.png" /></figure><blockquote><strong>TL;DR:</strong> Manually comparing PDF versions can be slow and error-prone. This blog shows how to use the JavaScript PDF Viewer to automatically detect content added, deleted, or modified between PDF revisions. Learn how to implement side-by-side comparison with the built-in PDF Comparer and build custom comparison experiences using semantic comparison APIs. These capabilities help reduce review effort, improve accuracy, and simplify document review processes.</blockquote><p>When a PDF document is updated, how do you quickly find what has changed from the previous version?</p><p>Reviewing both versions page by page can be time-consuming, especially when working with lengthy documents. Important changes can easily go unnoticed, making the review process more difficult.</p><p>The Syncfusion <a href="https://www.syncfusion.com/pdf-viewer-sdk/javascript-pdf-viewer">JavaScript PDF Viewer</a> in the <a href="https://help.syncfusion.com/common/essential-studio/release-notes/v35.1.37">2026 Volume 3 release</a> simplifies <a href="https://www.syncfusion.com/pdf-viewer-sdk/compare-documents">PDF document comparison</a>. Developers can use the built-in <strong>PdfComparer</strong> component to compare documents side by side or use the <strong>semanticTextCompare()</strong> API to build custom comparison experiences within their applications.</p><p>Let’s explore both approaches and see how to implement them.</p><h3>What does PDF document comparison do?</h3><p>PDF document comparison identifies text differences between two versions of a document. It helps reviewers find:</p><ul><li><strong>Added text:</strong> Content introduced in the modified document.</li><li><strong>Deleted text</strong>: Content present in the original document but removed from the updated version.</li><li><strong>Modified text</strong>: Existing content that has changed.</li></ul><p>For example, a contract review application can compare two revisions and direct reviewers to updated clauses instead of asking them to reread the entire document.</p><p>Semantic comparison focuses on text changes rather than every visual difference in a PDF’s layout, images, or formatting.</p><h3>Compare PDF versions using the built-in PDF Comparer</h3><p>If your application needs a ready-made comparison interface, use the <strong>PdfComparer</strong> component. It displays the original and modified documents side by side, with a differences panel for navigating detected changes.</p><p>The interface includes three areas:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*rkbChvMP4x3dtc3_a96KzQ.png" /></figure><p>Users can select a difference in the panel to jump to the corresponding content in both documents. This makes the built-in comparer a practical choice when you want to add PDF comparison without building the entire interface yourself.</p><h3>Get started with PDF comparison</h3><p>The following example initializes the PDF Comparer with two sample documents.</p><p><strong>Step 1: Add the Syncfusion resources</strong></p><p>Create an HTML file and include the Syncfusion Essential JS 2 stylesheet and JavaScript bundle.</p><p><strong>Step 2: Initialize the comparer</strong></p><p>Create a container for the comparer, provide the paths to the original and modified PDFs, and specify the PDF Viewer resource URL.</p><p><strong>index.html</strong></p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html lang=&quot;en&quot;&gt;<br>&lt;head&gt;<br>  &lt;meta charset=&quot;utf-8&quot; /&gt;<br>  &lt;title&gt;PDF Document Comparison&lt;/title&gt;<br><br>  &lt;link<br>    href=&quot;https://cdn.syncfusion.com/ej2/34.2.4/fluent2.css&quot;<br>    rel=&quot;stylesheet&quot; /&gt;<br><br>  &lt;script<br>    src=&quot;https://cdn.syncfusion.com/ej2/34.2.4/dist/ej2.min.js&quot;<br>    type=&quot;text/javascript&quot;&gt;&lt;/script&gt;<br><br>  &lt;style&gt;<br>    html, body {<br>      margin: 0;<br>      padding: 0;<br>      height: 100%;<br>      width: 100%;<br>    }<br><br>    #comparer-container {<br>      height: 100%;<br>      width: 100%;<br>    }<br>  &lt;/style&gt;<br>&lt;/head&gt;<br>&lt;body&gt;<br>  &lt;div id=&quot;comparer-container&quot;&gt;&lt;/div&gt;<br><br>  &lt;script&gt;<br>    const comparer = new ej.pdfviewer.PdfComparer({<br>      originalDocumentPath:<br>        &quot;https://cdn.syncfusion.com/content/pdf/original-document.pdf&quot;,<br>      modifiedDocumentPath:<br>        &quot;https://cdn.syncfusion.com/content/pdf/modified-document.pdf&quot;,<br>      resourceUrl:<br>        &quot;https://cdn.syncfusion.com/ej2/34.2.4/dist/ej2-pdfviewer-lib&quot;<br>    });<br><br>    comparer.appendTo(&quot;#comparer-container&quot;);<br>  &lt;/script&gt;<br>&lt;/body&gt;<br>&lt;/html&gt;</pre><p>Replace the sample PDF URLs with the documents your application needs to compare. Make sure the documents are accessible to the browser and that the resource URL matches the Syncfusion version used by your project.</p><p>Once the documents load, the comparer analyzes their text and displays the detected differences.</p><figure><img alt="Built-in PDF Comparer" src="https://cdn-images-1.medium.com/max/938/0*vKFWYvtv8bSae4en.png" /><figcaption>Built-in PDF Comparer</figcaption></figure><h3>Customize the comparison highlights</h3><p>Different applications may need different visual indicators for document changes. For example, a contract review tool might use one color for deleted text and another for added text.</p><p>Use the <a href="https://ej2.syncfusion.com/javascript/documentation/api/pdfcomparer/index-default#comparisonoptions">comparisonOptions</a> property to configure highlight colors, opacity, and visibility.</p><pre>const comparisonOptions = {<br>  beforeColor: &quot;#F17720&quot;,<br>  afterColor: &quot;#0474BA&quot;,<br>  beforeColorOpacity: 0.4,<br>  afterColorOpacity: 0.4,<br>  enableHighlights: true<br>};<br><br>const comparer = new ej.pdfviewer.PdfComparer({<br>  originalDocumentPath:<br>    &quot;https://cdn.syncfusion.com/content/pdf/original-document.pdf&quot;,<br>  modifiedDocumentPath:<br>    &quot;https://cdn.syncfusion.com/content/pdf/modified-document.pdf&quot;,<br>  resourceUrl:<br>    &quot;https://cdn.syncfusion.com/ej2/34.2.4/dist/ej2-pdfviewer-lib&quot;,<br>  comparisonOptions: comparisonOptions<br>});<br><br>comparer.appendTo(&quot;#comparer-container&quot;);</pre><p>In this example, deleted content in the original document is highlighted in orange, while added content in the modified document is highlighted in blue. The opacity settings control how strongly the highlights appear.</p><figure><img alt="Custom text comparison" src="https://cdn-images-1.medium.com/max/1024/0*6ell_c0MJYHyrfUE.gif" /><figcaption>Custom text comparison</figcaption></figure><p>You can also hide the differences panel when users need more space to read the documents. Set <a href="https://ej2.syncfusion.com/javascript/documentation/api/pdfcomparer/index-default#enabledifferencepanel">enableDifferencePanel</a> to <strong>false</strong>:</p><pre>const comparer = new ej.pdfviewer.PdfComparer({<br>  originalDocumentPath:<br>    &quot;https://cdn.syncfusion.com/content/pdf/original-document.pdf&quot;,<br>  modifiedDocumentPath:<br>    &quot;https://cdn.syncfusion.com/content/pdf/modified-document.pdf&quot;,<br>  resourceUrl:<br>    &quot;https://cdn.syncfusion.com/ej2/34.2.4/dist/ej2-pdfviewer-lib&quot;,<br>  comparisonOptions: comparisonOptions,<br>  enableDifferencePanel: false<br>});<br><br>comparer.appendTo(&quot;#comparer-container&quot;);</pre><p>The inline highlights remain available, while the side panel is hidden.</p><figure><img alt="Hide the differences panel" src="https://cdn-images-1.medium.com/max/938/0*E_kj0Hwb5W2Vkec6.png" /><figcaption>Hide the differences panel</figcaption></figure><h3>Keep both documents synchronized</h3><p>When reviewers scroll through one document, they often need to find the same section in the other. Synchronized navigation reduces this extra work by keeping scrolling and zooming aligned.</p><p>Enable it with the <strong>enableSyncScrolling</strong> property:</p><pre>const comparer = new ej.pdfviewer.PdfComparer({<br>  originalDocumentPath:<br>    &quot;https://cdn.syncfusion.com/content/pdf/original-document.pdf&quot;,<br>  modifiedDocumentPath:<br>    &quot;https://cdn.syncfusion.com/content/pdf/modified-document.pdf&quot;,<br>  resourceUrl:<br>    &quot;https://cdn.syncfusion.com/ej2/34.2.4/dist/ej2-pdfviewer-lib&quot;,<br>  comparisonOptions: comparisonOptions,<br>  enableSyncScrolling: true<br>});<br><br>comparer.appendTo(&quot;#comparer-container&quot;);</pre><p>This setting is useful when reviewers need to move between corresponding sections in long documents.</p><p>For additional configuration options, see the <a href="https://help.syncfusion.com/document-processing/pdf/pdf-viewer/javascript-es6/semantic-text-comparison/overview">PDF Comparer documentation</a> and explore the <a href="https://document.syncfusion.com/demos/pdf-viewer/javascript/#/bootstrap5/pdfviewer/semantic-text-comparison.html">live demo</a>.</p><h3>Build a custom PDF comparison interface</h3><p>The built-in comparer is a good fit for applications that need a ready-made review experience. However, some applications require a different layout or need to integrate comparison results into an existing workflow.</p><p>For example, you might want to:</p><ul><li>Display the documents inside a custom dashboard or modal.</li><li>Keep the PDF Viewer’s existing tools and custom toolbar.</li><li>Build your own differences panel or change log.</li><li>Use detected differences in an approval workflow.</li></ul><p>In these cases, initialize two <strong>PdfViewer</strong> instances and compare them using the <a href="https://ej2.syncfusion.com/javascript/documentation/api/pdfviewer/index-default#semantictextcompare">semanticTextCompare()</a> API.</p><h3>How custom comparison works</h3><p>The implementation follows four steps:</p><ul><li>Load the original PDF into the first viewer.</li><li>Load the modified PDF into the second viewer.</li><li>Call <strong>semanticTextCompare()</strong> to compare their text.</li><li>Use the returned results to display differences in your own interface.</li></ul><p>This approach gives you more control over the layout and how comparison results are presented. In return, your application must manage the viewer layout, loading state, navigation, and comparison controls.</p><h3>Implement semantic comparison</h3><p>The following example creates two PDF Viewer instances, synchronizes their navigation, and adds controls to compare documents and clear comparison results.</p><p><strong>index.html</strong></p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html lang=&quot;en&quot;&gt;<br>&lt;head&gt;<br>  &lt;meta charset=&quot;utf-8&quot; /&gt;<br>  &lt;title&gt;Custom PDF Comparison&lt;/title&gt;<br><br>  &lt;link<br>    href=&quot;https://cdn.syncfusion.com/ej2/34.2.4/fluent2.css&quot;<br>    rel=&quot;stylesheet&quot; /&gt;<br><br>  &lt;script<br>    src=&quot;https://cdn.syncfusion.com/ej2/34.2.4/dist/ej2.min.js&quot;<br>    type=&quot;text/javascript&quot;&gt;&lt;/script&gt;<br><br>  &lt;style&gt;<br>    html, body {<br>      margin: 0;<br>      height: 100%;<br>    }<br><br>    #controls {<br>      display: flex;<br>      gap: 8px;<br>      padding: 8px;<br>    }<br><br>    #container {<br>      display: flex;<br>      height: calc(100vh - 50px);<br>    }<br><br>    #pdfViewer1, #pdfViewer2 {<br>      width: 50%;<br>      height: 100%;<br>    }<br>  &lt;/style&gt;<br>&lt;/head&gt;<br>&lt;body&gt;<br>  &lt;div id=&quot;controls&quot;&gt;<br>    &lt;button id=&quot;compareButton&quot; type=&quot;button&quot; disabled&gt;<br>      Compare documents<br>    &lt;/button&gt;<br>    &lt;button id=&quot;syncButton&quot; type=&quot;button&quot;&gt;<br>      Disable sync<br>    &lt;/button&gt;<br>    &lt;button id=&quot;clearButton&quot; type=&quot;button&quot; disabled&gt;<br>      Clear comparison<br>    &lt;/button&gt;<br>  &lt;/div&gt;<br><br>  &lt;div id=&quot;container&quot;&gt;<br>    &lt;div id=&quot;pdfViewer1&quot;&gt;&lt;/div&gt;<br>    &lt;div id=&quot;pdfViewer2&quot;&gt;&lt;/div&gt;<br>  &lt;/div&gt;<br><br>  &lt;script&gt;<br>    const resourceUrl =<br>      &quot;https://cdn.syncfusion.com/ej2/34.2.4/dist/ej2-pdfviewer-lib&quot;;<br><br>    const pdfViewer1 = new ej.pdfviewer.PdfViewer({<br>      documentPath:<br>        &quot;https://cdn.syncfusion.com/content/pdf/original-document.pdf&quot;,<br>      resourceUrl: resourceUrl<br>    });<br><br>    const pdfViewer2 = new ej.pdfviewer.PdfViewer({<br>      documentPath:<br>        &quot;https://cdn.syncfusion.com/content/pdf/modified-document.pdf&quot;,<br>      resourceUrl: resourceUrl<br>    });<br><br>    let loadedCount = 0;<br>    let synchronizationEnabled = true;<br>    let comparisonCreated = false;<br><br>    function onDocumentLoaded() {<br>      loadedCount++;<br><br>      if (loadedCount === 2) {<br>        pdfViewer1.syncViewers(<br>          pdfViewer2,<br>          synchronizationEnabled<br>        );<br><br>        document.getElementById(&quot;compareButton&quot;).disabled = false;<br>      }<br>    }<br><br>    pdfViewer1.documentLoad = onDocumentLoaded;<br>    pdfViewer2.documentLoad = onDocumentLoaded;<br><br>    document.getElementById(&quot;compareButton&quot;)<br>      .addEventListener(&quot;click&quot;, async function () {<br>        if (loadedCount !== 2) {<br>          return;<br>        }<br><br>        const options = {<br>          beforeColor: &quot;#F17720&quot;,<br>          afterColor: &quot;#0474BA&quot;,<br>          beforeColorOpacity: 0.4,<br>          afterColorOpacity: 0.4,<br>          enableHighlights: true<br>        };<br><br>        const result = await pdfViewer1.semanticTextCompare(<br>          pdfViewer2,<br>          options<br>        );<br><br>        console.log(&quot;Comparison results:&quot;, result);<br>        comparisonCreated = true;<br>        document.getElementById(&quot;clearButton&quot;).disabled = false;<br>      });<br><br>    document.getElementById(&quot;syncButton&quot;)<br>      .addEventListener(&quot;click&quot;, function () {<br>        synchronizationEnabled = !synchronizationEnabled;<br><br>        pdfViewer1.syncViewers(<br>          pdfViewer2,<br>          synchronizationEnabled<br>        );<br><br>        this.textContent = synchronizationEnabled<br>          ? &quot;Disable sync&quot;<br>          : &quot;Enable sync&quot;;<br>      });<br><br>    document.getElementById(&quot;clearButton&quot;)<br>      .addEventListener(&quot;click&quot;, function () {<br>        if (!comparisonCreated) {<br>          return;<br>        }<br><br>        pdfViewer1.removeSemanticTextCompare(pdfViewer2);<br>        comparisonCreated = false;<br>        this.disabled = true;<br>      });<br><br>    pdfViewer1.appendTo(&quot;#pdfViewer1&quot;);<br>    pdfViewer2.appendTo(&quot;#pdfViewer2&quot;);<br>  &lt;/script&gt;<br>&lt;/body&gt;<br>&lt;/html&gt;</pre><p>The example uses the same sample documents as the built-in comparer. Replace them with your own document URLs when integrating the code into an application.</p><p>The Compare button calls <strong>semanticTextCompare()</strong> and logs the returned result to the browser console. The result contains structured information about detected differences, organized by document and page. You can use this data to build a custom differences panel, change log, or approval interface.</p><p>The synchronization button enables or disables synchronized navigation. The Clear comparison button calls <strong>removeSemanticTextCompare()</strong> to remove the comparison results while preserving user-created annotations.</p><figure><img alt="Show or hide difference highlights" src="https://cdn-images-1.medium.com/max/1024/0*7Lx2Q4vWu__0vmpO.gif" /><figcaption>Show or hide difference highlights</figcaption></figure><h3>Use the comparison results in your application</h3><p>The <strong>semanticTextCompare()</strong> method returns a structured result that includes:</p><ul><li><strong>originalDocumentAnnotations</strong>: detected differences associated with the original document.</li><li><strong>modifiedDocumentAnnotations</strong>: detected differences associated with the modified document.</li><li><strong>totalTextDiffCount</strong>: the total number of unique text differences detected.</li></ul><p>These results allow you to build a custom experience instead of relying on the built-in differences panel. For example, you could list changes by page, display a summary of the differences, or connect the results to an approval process.</p><p>Note that annotation text may also appear as added content in comparison results. If your workflow needs to clear the comparison results while keeping user-created annotations, use <a href="https://ej2.syncfusion.com/javascript/documentation/api/pdfviewer/index-default#removesemantictextcompare">removeSemanticTextCompare()</a>.</p><p>For a complete working reference, see the <a href="https://github.com/SyncfusionExamples/javascript-pdf-viewer-examples/tree/master/Semantic%20Text%20Comparison/Programmatically%20get%20differences">GitHub example for custom semantic PDF comparison</a>.</p><h3>Which comparison approach should you use?</h3><p>Choose the built-in comparer when you want a ready-made side-by-side interface with a differences panel. Choose the custom approach when your application needs a different layout, custom navigation, or direct access to comparison results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*L2J0RPGayNjLl8M38huayQ.png" /></figure><h3>Frequently Asked Questions</h3><ol><li><strong>When should I use the built-in PDF Comparer instead of a custom implementation?<br></strong>Use <strong>PdfComparer</strong> when you need a ready-made side-by-side interface with a differences panel. Choose the custom approach when you need full control over the layout, navigation, or presentation of comparison results.</li><li><strong>Can I create my own differences panel?<br></strong>Yes. The <strong>semanticTextCompare()</strong> API returns structured comparison results that you can use to create a custom panel, change log, or review workflow.</li><li><strong>Can I customize comparison highlight colors?<br></strong>Yes. Configure <strong>beforeColor</strong>, <strong>afterColor</strong>, <strong>beforeColorOpacity</strong>, and <strong>afterColorOpacity</strong> through the comparison options.</li><li><strong>Will clearing comparison results remove user-created annotations?<br></strong>The <strong>removeSemanticTextCompare()</strong> API is intended to remove semantic comparison results while preserving other user-created annotations. Test this behavior with your target Syncfusion version and annotation workflow.</li><li><strong>Does PDF comparison detect every visual change?<br></strong>No. Semantic comparison focuses on text differences. Changes to layout, images, or other visual elements may not be represented as text differences.</li></ol><h3>Conclusion</h3><p>Comparing PDF versions does not have to mean checking every page manually. Syncfusion <a href="https://help.syncfusion.com/document-processing/pdf/pdf-viewer/javascript-es6/overview">JavaScript PDF Viewer</a> provides two ways to build a better review experience: use <strong>PdfComparer</strong> for a ready-made interface or use <strong>semanticTextCompare()</strong> to create a custom workflow around the results.</p><p>Explore the <a href="https://help.syncfusion.com/document-processing/pdf/pdf-viewer/javascript-es6/semantic-text-comparison/overview">documentation</a> and <a href="https://document.syncfusion.com/demos/pdf-viewer/javascript/#/bootstrap5/pdfviewer/semantic-text-comparison.html">live demos</a> to see the feature in action. Existing Syncfusion customers can download the latest release from the License &amp; Downloads page, while new users can get started with a 30-day free trial.</p><p>For questions or feedback, visit the Syncfusion <a href="https://www.syncfusion.com/forums">support forums</a>, <a href="https://support.syncfusion.com/">support portal</a>, or <a href="https://www.syncfusion.com/feedback">feedback portal</a>.</p><h3>Related Blogs</h3><ul><li><a href="https://www.syncfusion.com/blogs/post/pdf-search-in-react-pdf-viewer">Why PDF Search Fails in React PDF Viewers and How to Fix It</a></li><li><a href="https://www.syncfusion.com/blogs/post/loan-document-workflow-react-pdfviewer">How to Build a Loan Document Workflow Using an Embedded React PDF Viewer</a></li><li><a href="https://www.syncfusion.com/blogs/post/role-based-lms-assignment-workflow-react-pdf-viewer">Build a Role-Based LMS with In-Document Learning Using a React PDF Viewer</a></li><li><a href="https://www.syncfusion.com/blogs/post/custom-toolbar-in-react-pdf-viewer">How to Build a Custom Toolbar in a React PDF Viewer?</a></li></ul><p><em>Originally published at </em><a href="https://www.syncfusion.com/blogs/post/how-to-compare-pdf-documents-in-javascript-using-syncfusion-pdf-viewer"><em>https://www.syncfusion.com</em></a><em> on October 30, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85c90843826c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/syncfusion/how-to-compare-pdf-documents-in-javascript-using-syncfusion-pdf-viewer-85c90843826c">How to Compare PDF Documents in JavaScript Using Syncfusion PDF Viewer</a> was originally published in <a href="https://medium.com/syncfusion">Syncfusion, Inc.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>