Adobe Captivate
Adobe Captivate
Welcome to the Adobe Captivate feedback page. Submit feature requests and bug reports to the Captivate team via this UserVoice page.
Please follow below steps while posting your enhancements & bugs
- Type your enhancements/bugs into the search field or choose from the categories in the sidebar.
- Check if enhancements or bugs submitted by others / upvote if you find similar to yours.
- If your feature idea or issue is not listed, post it.
- Upvote the ideas if you like.
The UserVoice feedback pages are for feature requests and bug reports only. Upload only content that you have permission to use and refrain from posting personal information (e.g. address, phone number, email, or credit card) or abusive content (spam, phishing links, vulgar language, etc.). Tips for submitting useful feedback
UserVoice is a third-party platform for product feedback. Please note that feedback is voluntary, and you give Adobe a right, to use feedback you provide without restrictions.
59 results found
-
ragesh.c@gds.ey.com
The new Adobe Captivate version does not support adding custom navigation elements like in the Classic version. Currently, the header and footer only allow limited customization—such as displaying the course name, page number, and TOC. There is no option to globally add essential navigation buttons like Back, Next, Glossary, or Resources across the course design. This limitation significantly impacts the flexibility and user experience of eLearning modules. Please consider reintroducing the ability to create and apply custom navigation players, as available in Adobe Captivate Classic.
1 vote -
[Feature] Control visibility of Design Options in the GUI
Problem:
All Design Options currently appear automatically in the menu, including those that are only used within other Design Options.Suggestion:
Add a property indesignOption.json(e.g.,visible: false) to control the visibility of a Design Option, so internal options are not shown in the menu.1 vote -
[Feature] Custom placeholder text and images in `designOption.json`
Problem:
Currently, placeholder text and images in Design Options are fixed. When placing a design option, a default image and Lorem Ipsum text appear.Suggestion:
Allow defining custom placeholder text and images directly in thedesignOption.jsonfor each widget or slide element.{ "tag": "slide-item-image", "placeholder": "placeholder.png", "customStyles": { "all": { "imageContainerStyles": {} } } }Benefit:
- Designers immediately see the expected image size and proportions.
- Placeholder text can indicate the function of the text (“Headline”, “Subtext”, etc.).
- Increases consistency and standardization across slides and projects.1 vote -
[Feature] Additional content wrapper for all design objects
Problem:
Currently,div.cp-widget-containerdirectly contains the widget elements.Suggestion:
It is recommended to introduce an additional content wrapper element belowdiv.cp-widget-containerfor all widgets (videos, text, images, quizzes, etc.). This new wrapper should hold the actual content and control its maximum width, while the outer container can still be used for full-width background styling.Benefits:
1. The existingdiv.cp-widget-containercan continue to provide full-width background styling (color, image, etc.), stretching across the entire slide.
2. The new inner wrapper (e.g.,div.cp-widget-container__inner) should hold the actual content and define a maximum content width to center and structure the layout consistently.…1 vote -
Improve the branding blocks Header and Footer
A few improvements that can be done in the branding blocks:
- Implement the option of making it persistent, so if the user scrolls through the content, the header or/and footer stays frozen above all the content.Ability to copy and paste the building blocks from one project to another, just so you don't have to remake all the configurations again in each of the projects. I have a dozen of projects that use branding blocks and need to build each one from scratch, this is annoying!
Include the header and footer in the Theme Editor, so when you apply…
2 votes -
Add the "Show/Hide during publish" option for Widget Blocks
I would like to create an infinite-scroll style course, but the Widget blocks (which provide the bulk of interactivity) can't be hidden during publish.
4 votes -
Copy and paste alignment and spacing from one block to another
I have about ten blocks on a particular slide. I manually set the alignment and spacing for each one, and then I had to do it again for tablet and mobile view. It would be nice if I could right-click on a block, copy the alignment and spacing, and then apply that same alignment and spacing to other blocks on the same slide, or for that matter, anywhere in my project.
3 votes -
Unrestrict element placement and size.
Currently unable to place button anywhere within the button field. All have to be together within the field, meaning limited design options. Also Icon buttons, should be able to re-size the icon within the button. Elements on screen, such as Text and Image, should be easily changed in size. At the moment, very restricted as to how the course will look. Classic Captivate was ideal as we had free rein over the design.
4 votes -
be able to copy paste from another project
In 2019 Captivate, you can copy/paste an entire slide or section of slides from one project to another. You don't seem to have this option in the new version. The clipboard doesn't seem to work across projects. This would be very helpful.
5 votes -
Objects click on widgets
One thing that I would love to see is that when using a widget, 'Objects clicked' could be used on the elements to control bespoke designed navigation buttons.
For instance, on the flipcard widget, it would be great to select each flipcard under 'Objects clicked' to control a NEXT button design purposely.
1 vote -
Create non-responsive projects
My organization has decided against responsive design. They actively discourage people from using non-desktop computer devices to complete training (concern about employees doing it outside of working hours). The new Captivate leaves us in a bind. We need to be able to design static non-responsive projects as we have always done in previous versions of Captivate.
We will likely never switch until this is restored in the product. If it doesn't come before Cp Classic EOL, we will need to find an alternative product.
39 votes -
Reorder position of elements in blocks
We should be able to reorder the elements of a block (title, image, subtile, etc.) by drag and drop. Example: the title could come before an image.
81 votesThis feature request is added to backlog and will consider it in future updates.
-
Divided Content Containers
Add the functionality to have content containers that only take up 1/2, 1/3, or maybe even 1/4th of the screen to enable more flexible and fuid content design within the slide.
An example would be to have a logo in the header on the page with the image on a 1/4th content divider and the header on a 3/4th text content divider. I understand there are already content presets with an image in it; however there is very limited flexibility in modifying the spacing and location of each item in the preset.
25 votes -
Simulation Components - Align and/or edit X/Y Coordinates
Need the ability to align components and see/edit the x/y coordinates for software simulations.
11 votes -
Retain items for whole project
In Captivate classic we could insert items (like a navigation toolbar) on one slide and display it for every slide thereafter in the project. Please include that option in this version.
17 votes -
add a module for us to create a slide header/footer
for the usual logo/couple of links menu (in my case, Main Menu and Glossary) make it a module that the user can apply and not a required slide format. As it is, the 'image' module is useless for this purpose.
38 votes -
Better Typography - Web fonts - options/weights
I only see a handful of google fonts as options and no Typekit fonts in captivate 12. It is missing big ones like Open Sans, Robot and Inter.
Allow us to use these or add our own custom web fonts.
System fonts do not include all weights and styles available.
While all other adobe apps support using alternative characters, Capitvate does not. You all have been one of the leaders in implementing web font technology and features, what happened?
8 votes -
Bug - Image Grid Text Overflow with Card Enabled
On the image grid design option "Image Grid Vertical C1" there is a bug when you enable the card component.
When the card is enabled, the text area for the caption and subtitle go past the boundary of the card. The issue persists at all content widths. If you make the content 100% wide and preview the slide, the text gets cut off.
If I add padding to the cards at 30px, it pushes the text back into bounds, but that doesn't fit with my other card designs.
If there is a way to adjust this in the JSON files…
2 votes -
Look at SCORM Package performance
Takes a very very long time even for a very small SCORM package to load. I use Moodle to host the SCORM package.
In comparison, while a 3MB H5P component loads in 3 seconds, it takes about 30 seconds for a 3mb SCORM package to load on screen.
5 votes -
Content width/Alignment % and title/text spacing should be the same for all blocks
An 80% width Image block is not the same width as an 80% Text block. It should align perfectly, but it doesn't (see image). I suppose I could adjust it with the new padding feature, but this really shouldn't be necessary. A certain % width should be the same for all blocks.
Also, the spacing between title and text is inconsistent. Maybe it's because an image block doesn't have body text, only Caption and Subtitle? But why?
Those basic details should be a given, it shouldn't be necessary to find workarounds, or fiddle with padding or line spacing to make…
1 vote
- Don't see your idea?