Acrobat for Windows and Mac
Help us improve Adobe Acrobat for Windows and Mac by sharing your feedback. Follow the instructions below to submit a feature request or bug report.
The UserVoice feedback pages are for feature requests and bug reports only. If your submission is not a product feature, suggestion or product question, it may be removed. Only upload content that you have permission to use and refrain from posting personal information (home address, phone number, email address, serial number, or credit card information). Spam, content that promotes illegal activity, vulgar or abusive language, or fraudulent or phishing links are not allowed on this platform.
UserVoice is a third-party platform for product feedback. The Adobe Acrobat DC team regularly reviews ideas and incorporates them into product planning discussions. We can’t guarantee specific features or development timelines, but we read every suggestion and respond where we can. Please note that feedback is voluntary, and if you provide feedback, you give Adobe the right to use it without restrictions.
For all other questions and discussions, visit the Support Community for Acrobat.
If you are still using Acrobat 11.x or other older versions, please note that those are no more supported by Adobe. Try out the latest, Acrobat DC.
In case your concern is not addressed in the latest version, please report the issue against Acrobat DC.
Please provide the following information. You can post a new idea or search for ideas already submitted.
How it works:
- Select the feedback forum for your product.
- Browse ideas and vote for the ones you like.
- You may also post a comment for the idea.
- If your feature idea or issue is not listed, post it.
- In order to get subscribed to an item for any updates from Adobe, you must vote for it and click the subscribe button.
For a new feature request:
- Brief title
- Description of desired feature
- Why the feature is needed
For a new bug:
- Brief title
- Steps to reproduce the issue
- Environment (OS, other related application versions, etc.)
- Expected result
- Observed result
Need support? Please visit Learn and Support to get started, find quick answers, engage with our vibrant community, and connect with Adobe staff.
-
combine word files in PDF in Acrobat DC
It doesn't work at all! PDF maker is not cooperating with Microsoft Office.It worked though in older version of Acrobat
12 votes -
Accessibility Problems with Images/Figures
I have a Microsoft Word file that has a number of images. I need to make an accessible PDF. I have entered alternate text for each image in MS Word. When I convert the Word file to PDF, the alternate text I had entered in MS Word is carried over to the PDF, which is what I want. The problem is that it puts all images/figures at the beginning of the tag tree no matter where the image comes in the document. When I look at the Reading Order for each page, it puts all images as the last item…
5 votesHi,
I have reported the issue to the Engineering Team and you may see it fixed in future releases.Thanks
Rachit -
[Bug not resolved] Incomplete "From" field when converting to PDF from Microsoft Outlook 2016
Bug not resolved.
In "From" field only shows the name of the email account but
doesn't show its email account between "< ... >", like in
previous releases.
System: Microsoft Windows 10 Pro x64 (updated) //
Microsoft Outlook 2016 (updated) // Adobe Acrobat Pro DC
2018.011.20038(*) Compare results with, for example, Foxit PhantomPDF addon for Outlook.
5 votesThanks for raising your concern, this is know issue and we are working on it.
Will keep you posted.Thanks,
Mridula -
PDFMaker Add-in causes Title: Failed error from MS Word 2016
An accessible MS Word 2016 docx, saved as a PDF with the Adobe PDFMaker Add-in enabled, creates a PDF when Accessibility Checked with Acrobat Pro 2017 results in a Title: Failed error. The same MS Word PDF created after disabling the PDFMaker Com Add-in no longer results in the Title:Failed error.
The Title: Failed error caused by PDFMaker is easily corrected by clicking "Fix it" in acrobat pro, but the document already has a title and this step should not be necessary. It's better to disable PDFMaker which is installed as part of Acrobat Pro 2017.
Please fix PDFMaker.
-
How do I provide website accessibility reports to the HIDOE Civil Rights Compliance Branch 7 pdfmaker title failed.pdf 545 KB -
How do I provide website accessibility reports to the HIDOE Civil Rights Compliance Branch 9 no pdfmaker add in.pdf 217 KB -
Acrobat Pro 2017 System Information.txt 3 KB -
Adobe_Chat_Transcript_5-1-20.pdf 20 KB -
How do I provide website accessibility reports to the HIDOE Civil Rights Compliance Branch.docx 253 KB
2 votesHi
Thanks for reporting the issue. We are aware of this bug with Office 2016 and it will be prioritized based on other work items.
Thanks
Tanvi -
-
PDF Maker (PowerPoint) crashes with long path to file
PDF Maker seems to crash for PowerPoint when the path name is long. I tested converting with a PPTX file in OneDrive, and it crashed when the path and filename length were 250.
1 voteHi
Thanks for reporting the issue. We are able to reproduce this and added it to our bug database. We will keep you posted on the progress.
Thanks
Tanvi -
Graphic conversion from Word was completely messed up
Most of the time, I've had no trouble with conversions of scientific graphics in Microsoft Word to the corresponding PDF images. This time it was really messed up! I've attached the Acrobat DC conversion and a similar conversion with another PDF converter program. The latter was a faithful translation of the Word image.
Can this be fixed?
1 voteThanks for sharing the file. We are able to reproduce the issue at our end. We have added it in our bug database.
Thanks
Tanvi
- Don't see your idea?