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.
- or
926 results found
-
Bug: Make click box reflect actual settings in Captivate
When hand cursor is turned on, the area where the hand cursor appears is MUCH larger than the area assigned in Captivate. Also why did you remove the true square box to make the corners rounded? And why do I have no control over this? I can make it a star but I can't make it square? Please explain the rationale behind this.
1 vote -
Review rendering of transparent background images
Transparent images in PNG or SVG format when used as background are showing a thin line like it was being tiled, even if the tile option is not selected.
In the example attached, I have a simple SVG with an angled corner used as background, and on the bottom-right corner it displays a line of the same colour.
The same happens with PNG images.
1 vote -
[Bug] Parent slide scrolls while overlay slide is active and scrolling
Version: 13.0
Problem:
When an overlay slide is opened and the parent slide is taller than the viewport, both the parent slide and the overlay slide scroll simultaneously when the overlay content is scrolled. This causes the user to lose focus on the overlay and disrupts the intended user experience.Consequences:
- Confusing focus shifts between the parent slide and the overlay slide
- Weakened UX for dialogs and lightbox content
- Accessibility issues, especially for keyboard navigationSuggestion:
- The parent slide should not scroll while the overlay slide is active and being scrolled.
- Only the overlay slide should scroll when its content exceeds the viewport height.
- If the overlay slide is smaller than the viewport, no scrolling should occur.Version: 13.0
Problem:
When an overlay slide is opened and the parent slide is taller than the viewport, both the parent slide and the overlay slide scroll simultaneously when the overlay content is scrolled. This causes the user to lose focus on the overlay and disrupts the intended user experience.Consequences:
- Confusing focus shifts between the parent slide and the overlay slide
- Weakened UX for dialogs and lightbox content
- Accessibility issues, especially for keyboard navigationSuggestion:
- The parent slide should not scroll while the overlay slide is active and being scrolled.
- Only the overlay slide…1 vote -
[Feature] Overlay slides should be fully customizable
Version: 13.0
Problem:
Overlay slides currently receive several automatic CSS properties that cannot be controlled:
- Padding on.cp-overlay-slide
- Padding on.cp-overlay-slide .cp-slide-wrapper
-min-heightvalues
-box-shadoweffectsThese defaults make it difficult to integrate overlays consistently into existing designs.
Suggestion:
Overlay slides should be customizable just like normal slides and appear exactly the same within the parent slide. Effects such as blur, box-shadow, etc. should be optional and configurable via the GUI.1 vote -
I am unable to export text-to-speech audio from Captivate. This was a problem for us in Captivate 12 and continues to be a problem with 13
I am unable to export text-to-speech audio from Captivate. This was a problem for us in Captivate 12 and continues to be a problem with 13. I attended the Adobe Learning Summit and spoke to the developers about it, but have not received a resolution.
1 vote -
Crashing during AI Avatar
I have had a couple of attempts to create an AI Avatar for an imported PowerPoint. I was recording for YouTube at the time, submitted the crash using the crash report but thought it might be beneficial to see what I was doing at the time.
https://youtu.be/GwG8bphGb1o1 vote -
[Bug] `textProps.fontWeight` is ignored during rendering
Version: 13.0
Problem:
textPropsvalues such asfontWeightset indesignOption.jsonare displayed correctly in the Captivate UI, but are ignored in the final rendering and overridden by inline styles (e.g.,font-weight: normal;). OthertextProps(liketextAlign) work as expected.{ "tag": "slide-item-subtitle", "preset": "text-body-6", "customStyles": { "all": {} }, "customProperties": { "alignmentAndSpacing": {}, "textProps": { "fontWeight": "600", "textAlign": "center" } } },In the rendered output, inline styles appear such as:
font-weight: normal;Impact:
- Inconsistent results between editor preview and actual output
- Paragraph styles cannot be reliably overridden
- UI feedback is misleading (shows correct formatting, but renders incorrectly)Expected behavior:
textPropsshould be respected during rendering and should not be overridden by generated inline styles.Version: 13.0
Problem:
textPropsvalues such asfontWeightset indesignOption.jsonare displayed correctly in the Captivate UI, but are ignored in the final rendering and overridden by inline styles (e.g.,font-weight: normal;). OthertextProps(liketextAlign) work as expected.{ "tag": "slide-item-subtitle", "preset": "text-body-6", "customStyles": { "all": {} }, "customProperties": { "alignmentAndSpacing": {}, "textProps": { "fontWeight": "600", "textAlign": "center" } } },In the rendered output, inline styles appear such as:
font-weight: normal;Impact:
- Inconsistent results between editor preview and actual output
- Paragraph styles cannot be reliably overridden
- UI feedback is misleading (shows correct…1 vote -
[Feature] Grid and Visible Borders for Design Options
Version: 13.0
Problem:
When working in Captivate, visual aids such as grids, borders, or width and height indicators are missing. Apart from the highlight shown when directly clicking a Design Option or on slide overflow, the positioning of elements is difficult to control – especially for complex layouts.Suggestion:
- Visible borders for Design Options and their sub-elements, optionally toggleable.
- Fully customizable background grid, similar to Adobe XD or Figma, for better layout orientation.
- Display of width and height measurements for placed elements.1 vote -
[Bug] Design Option “Image” does not respond correctly to grid styling
Version: 12.6
Problem:
The “Image” design option partially fails to respond to grid styling defined in thedesignOption.json. The elementcontainer-image-textdoes not occupy the designated grid-area because it is not a direct child of thecontainer-image-cardelement where the grid is applied.In Chrome DevTools, it is visible that the instruction
grid-area: 1 / 1 / span 1 / span 1;has no effect because the target element does not participate in the grid context.
See screenshot:design-options_image-01.png1 vote -
[Feature] Support for Character Styles for Inline Text
Version: 13.0
Problem:
Currently, Captivate only supports paragraph-level formatting (Paragraph Styles). There is no way to define reusable character styles for quick and consistent inline emphasis. The existing “Highlight” inline element is too limited (no padding, margin, border, border-radius, etc.), leading to inconsistent workarounds and unnecessary manual inline formatting.Use Cases:
- Highlighting key terms
- Inline quotes / badges
- Keyboard shortcuts / keycaps
- Code snippets
- Labels / status indicatorsSuggestion:
Introduce freely definable character styles supporting:
- color, background-color
- font properties
- padding, margin
- border, border-radiusConfigurable in:
- GUI (Theme-Editor)
-theme.jsonBenefits:
- consistent corporate branding via global styling
- improved readability and learner orientation
- reduced manual inline formatting
- clearer emphasis of instructional key termsVersion: 13.0
Problem:
Currently, Captivate only supports paragraph-level formatting (Paragraph Styles). There is no way to define reusable character styles for quick and consistent inline emphasis. The existing “Highlight” inline element is too limited (no padding, margin, border, border-radius, etc.), leading to inconsistent workarounds and unnecessary manual inline formatting.Use Cases:
- Highlighting key terms
- Inline quotes / badges
- Keyboard shortcuts / keycaps
- Code snippets
- Labels / status indicatorsSuggestion:
Introduce freely definable character styles supporting:
- color, background-color
- font properties
- padding, margin
- border, border-radiusConfigurable in:
- GUI (Theme-Editor)
-theme.jsonBenefits:…
1 vote -
[Feature] Option for image container to grow with text in the “Image” Design Option
Version: 12.6
Problem:
Currently, the image in the "Image" Design Option does not grow when the text blockcontainer-image-textincreases in height. There is no setting in either the Captivate GUI or thedesignOption.jsonto scale the image vertically along with its content.
In responsive layouts (e.g., hero sections, split layouts), this leads to unbalanced designs, awkward proportions, and unnecessary whitespace.
See screenshotsdesign-options_image-02.pnganddesign-options_image-03.png.Suggestion:
Add an optional setting that allows the image to:
- grow vertically with the text container
- maintain its aspect ratio (e.g., viaobject-fit)
- adapt responsively to varying content heights
- optionally use amin-heightto prevent layout collapseThese options should be configurable both in the GUI and in the
designOption.json.Note:
The behavior should remain optional. In some layouts, a fixed height is still desired — ideally configurable separately for each device (Desktop, Tablet, Mobile).
See screenshotdesign-options_image-04.pngVersion: 12.6
Problem:
Currently, the image in the "Image" Design Option does not grow when the text blockcontainer-image-textincreases in height. There is no setting in either the Captivate GUI or thedesignOption.jsonto scale the image vertically along with its content.
In responsive layouts (e.g., hero sections, split layouts), this leads to unbalanced designs, awkward proportions, and unnecessary whitespace.
See screenshotsdesign-options_image-02.pnganddesign-options_image-03.png.Suggestion:
Add an optional setting that allows the image to:
- grow vertically with the text container
- maintain its aspect ratio (e.g., viaobject-fit)
- adapt responsively to varying content heights…1 vote -
[Feature] Custom layout slides with freely configurable Design Options
Problem:
New content slides can currently only be created based on predefined layout categories (e.g., Comparison, Meet the Team). Each layout only allows importing a fixed set of Design Options defined in its associateddesignOption.json. Additional components cannot be added, which makes layouts unnecessarily rigid and difficult to adapt to custom design requirements or corporate branding.Example:
Meet the Team only allowsparagraphandimage-grid. Adding an additional paragraph beneath the grid is not possible.{ "type": "Meet the Team", "name": "$$name", "description": "$$description", "designOptionId": "LAYOUTS_MEET_THE_TEAM", "isDefault": false, "version": "1.0", "thumbnail": "thumbnail.png", "styles": [ { "tag": "paragraph", "designOptionId": "MTT_PARAGRAPH_OPTION_1" }, { "tag": "image-grid", "designOptionId": "IMAGE_GRID_MTT_OPTION_1" } ] }Suggestion:
Enable support for custom layout slides, where the correspondingdesignOption.jsoncan contain any components the author needs. This would allow instructional designers to create rich, reusable layout templates for both slide-based content and longpages.Problem:
New content slides can currently only be created based on predefined layout categories (e.g., Comparison, Meet the Team). Each layout only allows importing a fixed set of Design Options defined in its associateddesignOption.json. Additional components cannot be added, which makes layouts unnecessarily rigid and difficult to adapt to custom design requirements or corporate branding.Example:
Meet the Team only allowsparagraphandimage-grid. Adding an additional paragraph beneath the grid is not possible.
…{ "type": "Meet the Team", "name": "$$name", "description": "$$description", "designOptionId": "LAYOUTS_MEET_THE_TEAM", "isDefault": false, "version": "1.0", "thumbnail": "thumbnail.png", "styles": [ { "tag": "paragraph", "designOptionId":1 vote -
Allow content creators to import .doc or .pdf text to populate a template.
If there were tags that could be placed into a word document that could call for a slide option in a project template, then the program could auto-populate text and images into predetermined slide options. This would allow for a rapid conversion to Captivate files when receiving only text, image and link content from authors.
Many of our authors are accustomed to a particular set of procedures for content development. We need a simple method to take the content provided and convert it to a Captivate project.
If there were <tag>s of some sort that could identify sections of text and their associated images and links to videos or other online content and then populate an appropriate slide template, that would be ideal. Tags could identify other design options as well, for example font style or shape colors or corner radius for buttons. Have a simple library of available tags. Then content creators who do not use Captivate can put in tags that would reduce the amount of time needed for the Captivate content team to fine tune the imported project.
Ideally, they would also be able to tag specific variables and object names as well. Some of our LMS integration is dependent on button object names and custom variables. These variables could mostly be handled by a custom template though, if that were an option, which it absolutely should be. Then it would just be making sure that the doc or pdf had the appropriate tag for the custom slide template with the appropriate custom variable options.
If there were tags that could be placed into a word document that could call for a slide option in a project template, then the program could auto-populate text and images into predetermined slide options. This would allow for a rapid conversion to Captivate files when receiving only text, image and link content from authors.
Many of our authors are accustomed to a particular set of procedures for content development. We need a simple method to take the content provided and convert it to a Captivate project.
If there were <tag>s of some sort that could identify sections of text…
1 vote -
Variables and Design Options
We all understand that Captivate 12 is "built around a template-based authoring approach, designed to streamline project creation with minimal effort." that's just great. And we all want a simple user interface for our content creators who are less technically savvy, which Captivate provides. That does not mean that the content administrators don't still need the ability to have custom templates with variables to integrate properly with their LMS (and in our case LRS). We have government mandated variable time requirements for slide dwell time and total lesson duration. We also have varying pass percentage requirements.
There are a large number of exchanges that have to happen to make sure that a given user / registration is launched with the appropriate injected values. That means that the variable must be accurate. Those variable should not have to be recreated ever, they should be selectable, custom variables that are options for any new project if they are in the options folder.
Currently, you have to copy a slide from a 'template project' somewhere on your computer. When you do that, with no apparent specific reason, Captivate creates a new variable. This, of course, breaks the logic and you must go through every slide with variables and make sure that a numerical suffix has not been added when pasting. There is no way to turn this off. Further, you cannot delete these ghost variables that end up being sometimes 50-100 randomly generated variables. You try to delete them, and even though those variables are used NOWHERE in the project, Captivate does not allow you to delete them. It is genuinely frustrating.
The entire variable and design option architecture is pretty broken. It is 'clunky' at best. I dont even want to think about how many hours I have had to waste fixing logic errors in a program that is supposed to be "designed to streamline project creation with minimal effort."
In our case, it has been anything but 'streamlined'
Our dev team is throttled by the Captivate teams decision making process, it is not good.
We want the simple interface and template, yes.
We MUST have the ability to create our own custom templates complete with custom variables that do not create a 1000 ghosts.
We all understand that Captivate 12 is "built around a template-based authoring approach, designed to streamline project creation with minimal effort." that's just great. And we all want a simple user interface for our content creators who are less technically savvy, which Captivate provides. That does not mean that the content administrators don't still need the ability to have custom templates with variables to integrate properly with their LMS (and in our case LRS). We have government mandated variable time requirements for slide dwell time and total lesson duration. We also have varying pass percentage requirements.
There are a large…
1 vote -
[Feature] Option for automatic display of timeline events (without click)
Problem:
In the current Timeline widget, each event must be clicked manually for its associated content (text/image) to appear.
This interaction pattern is not ideal for all learning scenarios — especially in linear or narrative timelines, repeated clicking can be distracting and offers little didactic value.Suggestion:
Add an option in the Captivate GUI and in thedesignOption.jsonto control the behavior:
- Manual (current behavior): The user clicks each event to reveal its content.
- Automatic: The content is always visible.
- For better user experience: The content appears with a smooth fade-in or motion animation when the event enters the viewport.Problem:
In the current Timeline widget, each event must be clicked manually for its associated content (text/image) to appear.
This interaction pattern is not ideal for all learning scenarios — especially in linear or narrative timelines, repeated clicking can be distracting and offers little didactic value.Suggestion:
Add an option in the Captivate GUI and in thedesignOption.jsonto control the behavior:
- Manual (current behavior): The user clicks each event to reveal its content.
- Automatic: The content is always visible.
- For better user experience: The content appears with a smooth fade-in or motion animation when the event…1 vote -
[Feature] New Widget for Expandable Single Sections (Disclosure / Details)
Background:
On longpages or compact content layouts, there is often a need for expandable single sections for supplementary content such as transcripts, glossaries, or additional information. An accordion widget is overkill for this purpose, as it requires multiple tabs and semantically implies a group behavior.Problem:
- The Accordion widget cannot currently be reduced to a single tab.
- Using a "pseudo-accordion" with only one panel is semantically incorrect and may negatively impact accessibility and user orientation.
- There is no dedicated widget to toggle individual content sections, making implementation cumbersome.Suggestion:
A dedicated widget based on the established HTML5<details>/<summary>pattern or a disclosure element. It should:
- Toggle a single content block open/closed
- Optionally scroll automatically
- Optionally support state persistence
- Clearly indicate visual states
- Be configurable via GUI anddesignOption.jsonBackground:
On longpages or compact content layouts, there is often a need for expandable single sections for supplementary content such as transcripts, glossaries, or additional information. An accordion widget is overkill for this purpose, as it requires multiple tabs and semantically implies a group behavior.Problem:
- The Accordion widget cannot currently be reduced to a single tab.
- Using a "pseudo-accordion" with only one panel is semantically incorrect and may negatively impact accessibility and user orientation.
- There is no dedicated widget to toggle individual content sections, making implementation cumbersome.Suggestion:
A dedicated widget based on the established HTML5 …1 vote -
ragesh.c@gds.ey.com
The new Adobe Captivate version does not allow placing objects in a custom order. It only supports drag-and-drop using predefined templates. For example, if we need to position titles, images, icons, or buttons freely on the slide, this flexibility is missing. Currently, all custom design options are limited, forcing us to use only what Captivate provides.
1 vote -
Add checkboxes with Select All or Deselect All when editing Table of Contents
When creating courses in Captivate, we often have over 100 slides, but we only want our users to have access to maybe 10 in the Table of Contents. In Captivate 12.6, I have to deselect each slide which is obnoxiously time consuming. The "eye" icon action should be replaced with check boxes with "Select All" or "Deselect All" options at the top.
1 vote -
Bug- Mac Users Have Different Text
When I create trainings, they work just as expected on Windows but if someone on a Mac opens it the text turns into a different font and is not matching my company branding as I designed it to.
1 vote -
Text Drag and Drop
I don't use the drag and drop because currently it is only for pictures. Would be nice to have the ability to have learners drag and drop text to other text.
1 vote
- Don't see your idea?