Digital Signature Not Working on PDF in Chrome or Mobile? Here’s What You Can Do

Are you trying to digitally sign a PDF in Google Chrome, only to find that the digital signature field does not work?

You are not alone. Many users encounter problems when a PDF containing a certificate-based digital signature field is opened directly in a web browser or on a mobile device.

The problem becomes even more frustrating when the same PDF works correctly in the desktop version of Adobe Acrobat or Adobe Acrobat Reader.

If you are using an official form for a government department, business, school, university, or other organization, simply telling users to “download the PDF” may not be a practical solution, particularly when many people access forms through smartphones.

So, what is actually happening, and what can you do?

Why Is the Digital Signature Not Working in Chrome/ Web Browser?

The first thing to understand is that there is a difference between a simple electronic signature and a certificate-based digital signature.

A simple electronic signature may involve typing a name, drawing a signature, or placing an image of a signature on a PDF.

A certificate-based digital signature uses a Digital ID/certificate to provide identity verification and document integrity.

Adobe’s documentation specifically describes certificate-based digital signatures as a separate type of signing mechanism.

This distinction is important because a PDF that requires a certificate-based digital signature may not behave the same way when opened inside a browser’s built-in PDF viewer.

Does Chrome Support PDF Digital Signatures?

Chrome can display and work with PDFs, and Adobe provides a Chrome extension with PDF tools including Fill & Sign functionality.

However, displaying a PDF and applying a certificate-based digital signature are not necessarily the same thing.

Adobe’s documentation for certificate-based digital signatures explains the desktop Acrobat workflow, where the user selects Use a certificate → Digitally sign and chooses a Digital ID.

For Acrobat Sign, Adobe separately supports electronic signatures and cloud-based digital signatures through supported browsers. Adobe lists current versions of Chrome, Edge, Firefox and Safari among supported browsers.

Therefore, if your PDF contains a traditional certificate-based digital-signature field that expects the user’s local Digital ID or certificate, opening the PDF directly in Chrome may not provide the same signing workflow as desktop Acrobat.

The Easiest Workaround: Open the PDF in Adobe Acrobat

If the PDF was designed to use a certificate-based digital signature, the first solution to try is:

1. Download the PDF.
2. Open it using Adobe Acrobat or Adobe Acrobat Reader on a supported desktop computer.
3. Locate the digital-signature field.
4. Select the field.
5. Select the appropriate Digital ID/certificate.
6. Complete the signing process.
7. Save the signed PDF.

Adobe’s documented workflow for certificate-based signing uses Acrobat or Acrobat Reader and a Digital ID.

This is different from simply adding a handwritten or typed signature.

What About Adobe Acrobat on Mobile?

This is where things can become confusing.

Adobe Acrobat on Android and iOS does support filling forms and adding a signature. Users can open a PDF, select the signature tool, draw or create a signature, and place it on the document.

However, that functionality should not automatically be interpreted as support for every type of certificate-based digital signature.

Adobe’s mobile documentation describes features such as:

• Filling text fields
• Selecting checkboxes
• Adding signatures
• Adding initials
• Requesting e-signatures

Certificate-based Digital ID signing is a different workflow from simply adding a signature annotation.

Therefore, if your government or business form specifically requires a Digital Signature Certificate (DSC) or certificate-based signature, testing the form on both desktop Acrobat and mobile Acrobat is important before making the form available to the public.

Electronic Signature vs Digital Signature

This is probably the most important distinction when designing your PDF form.

Electronic Signature

An electronic signature can include:

• Typed name
• Drawn signature
• Uploaded signature image
• Signature captured through an e-signature service

Adobe Acrobat on the web supports filling and signing documents using these types of tools.

Certificate-Based Digital Signature

A certificate-based digital signature uses a Digital ID and provides stronger identity and document-integrity functionality.

Adobe’s desktop Acrobat documentation provides a dedicated Use a certificate workflow for this type of signature.

For forms used by government agencies, this distinction can be critical.

Why Does the Same PDF Work on One Device but Not Another?

A PDF can behave differently depending on:

• Browser
• Operating system
• PDF viewer
• Acrobat version
• Mobile vs desktop
• PDF form technology
• Digital ID configuration
• Security settings
• Whether the PDF uses an XFA form

For example, Adobe states that XFA forms are not supported in Acrobat on mobile.

This means that simply testing a PDF on one computer is not enough if the intended audience will use different devices.

Check Whether Your PDF Uses an XFA Form

If your PDF was created using Adobe LiveCycle Designer or uses an XFA-based form structure, mobile compatibility can be a significant issue.

Adobe specifically states that dynamic and static XFA forms are not supported in Acrobat on mobile.

If your form is intended for a large public audience, especially mobile users, consider checking the underlying form technology before deployment.

A Better Solution for Government and Public Forms

If you are responsible for a government or institutional form, don’t simply add a note saying:

“Digital signature is not supported in your browser.”

That tells the user what is wrong but does not give them a practical solution.

Instead, provide a clear signing path.

For example:

Option 1: Desktop certificate signing

Download the PDF → Open in Adobe Acrobat/Reader → Apply Digital Signature → Save → Upload/Submit.

Option 2: Browser-based e-signature

Use an Adobe Acrobat Sign workflow if the organization’s requirements allow an electronic or cloud-based digital signature. Adobe supports e-signing workflows through its web service.

Option 3: Mobile-friendly form

If most users are expected to complete the form on smartphones, redesign the process around a web-based or mobile-compatible e-signature workflow instead of requiring users to install desktop software.

Can Adobe Make a PDF Work in Every Browser?

Not necessarily.

The compatibility problem is not always caused by the PDF itself. The browser, PDF viewer, form technology and type of signature all matter.

Adobe’s current documentation lists Chrome, Edge, Firefox and Safari as supported browsers for Acrobat Sign.

However, that does not mean that every certificate-based digital-signature PDF will work identically in every browser’s built-in PDF viewer.

If your form requires a specific Digital ID, certificate, USB token, smart card or other signing mechanism, the complete signing workflow needs to be tested.

What Should You Do If Your PDF Works Only After Downloading?

If downloading the PDF and opening it in Acrobat solves the problem, you can provide clear instructions to users.

For example:

Having trouble signing this PDF?

1. Download the PDF to your device.
2. Open it using Adobe Acrobat Reader.
3. Complete the required fields.
4. Select the digital-signature field.
5. Select your Digital ID/certificate.
6. Sign and save the document.
7. Upload the signed PDF using the required submission method.

This is much more useful than simply telling users that the browser does not support the feature.

What If Users Are Mostly on Mobile?

This is where organizations should reconsider the overall form design.

If the majority of your users access the form through smartphones, requiring them to download a PDF, install desktop software, configure a Digital ID and then digitally sign the document can create unnecessary friction.

Adobe’s mobile Acrobat application supports Fill & Sign functionality, but organizations should distinguish this from certificate-based digital-signature requirements.

If a legally or administratively required certificate-based DSC is mandatory, a web-based signing service or an appropriately designed application workflow may be more suitable.

How to Make a Government PDF More Compatible

If you are creating or maintaining a government form, consider these points:

Use Standard PDF Forms Where Possible

AcroForms are broadly supported for entering information. Adobe states that AcroForms can be filled from different platforms, although editing the form structure itself is a desktop function.

Avoid Unsupported XFA Forms for Mobile Users

If mobile access is important, avoid relying on XFA forms because Adobe does not support XFA forms in Acrobat on mobile.

Clearly Explain the Signing Method

Tell users whether they need:

• A normal electronic signature
• An Adobe e-signature
• A Digital ID
• A Digital Signature Certificate
• A USB token
• Desktop Acrobat

Test on Multiple Platforms

Before publishing the form, test it on:

• Windows + Chrome
• Windows + Edge
• Windows + Firefox
• macOS + Safari
• Android + Chrome
• iPhone + Safari
• Acrobat Reader desktop
• Acrobat mobile

Testing only one computer is not enough for a public-facing government form.

Final Thoughts

When a digital signature does not work on a PDF opened in Chrome, the problem is not necessarily that the PDF is broken.

The key question is what type of signature the PDF requires.

A simple electronic signature can be supported through web and mobile workflows, while a certificate-based digital signature may require a different signing environment. Adobe currently provides browser-based e-signing options through Acrobat Sign and desktop certificate-based signing through Acrobat/Reader.

For organizations serving a large public audience, especially government agencies, the best approach is to design the form around the actual devices users have. If mobile users are the majority, a workflow that depends entirely on desktop PDF software may create unnecessary problems.

The goal should not simply be to tell users that “digital signatures are not supported.” The form should provide a clear, tested path for completing and signing the document on the platforms the organization expects its users to use.