Skip to main content

Filter by idea status

10000+ Ideas

Back to top of the list
ahmed hamed elsaidInspiring

Adding Fills and Strokes in the Properties Panel!Open for Voting

Property panel is great when dealing with complicated and nested shape layers.But adding fills, strokes, rectangles, or modifiers like merge paths, offset paths needs you to go in the timeline.It will be really easier if there was an ‘add’ bottom in the Properties panel, then what you choose to be added is added to the selected properties!My Request:Adding ‘Add’ button to the Properties panel for adding special shape groups like the one beside the ‘Content’ property group.How it will help my workflow:It is very helpful when dealing with complex shape layer and stylize them!Upvote if you like the Idea!Property panel 

3
othmanqw12
Forum|Forum|6 months ago
Todd_Morgan
Todd_MorganLegend

When previewing would be great to have a toggle to show/hide guide tracks.Open for Voting

Often rendering social media files with safe area guide layer that would be nice to not see when playback

2
Forum|Forum|6 months ago
Artimuscode
ArtimuscodeParticipant

Motion is great. We need keyframe animation timeline and maybe a simple rigging system.Open for Voting

Motion feature is limited and should allow for keyframe based animation. Setting start and endpoint per object or group. 

1
StevePhillips
Forum|Forum|6 months ago
just eirik
just eirikKnown Participant

P: Precise aspect ratio input with NUMBERSOpen for Voting

I am so tired of adobe not listening to what we want. And I’m even more tired of adobe not implementing the most basic functionality.  PLEASE let us input aspect ratios with numbers! This can’t possibly be too much to ask.Been paying for years and years and still have to put up with lack of features that already exist in Classic and this one is a small one too. It feels bad, Adobe.

0
just eirik
Forum|Forum|6 months ago
curious_Eagle5C09
curious_Eagle5C09Participant

please add 4K resolution to Nano banana pro modelReleased

please add 4K resolution to Nano banana pro model

2
Hajar Toutsi
Forum|Forum|6 months ago
Gib HansonParticipant

Function to "remove all transitions from selected clips"Open for Voting

I often have to produce clean versions of videos I edit, which currently involves scrolling along the entire timeline and selecting/deleting each clip transition manually. It takes time and is easy to miss a few. It would be awesome if there was a function someplace in the clip menu or timeline context menu to remove all transitions from clips I've selected in one shot.

6
AndrewTheGreat
Forum|Forum|6 months ago
daring_Cascade3810
daring_Cascade3810Participant

P: Light Tab 2.0 & Updating Effects TabOpen for Voting

Suggestion to make Light and Effects tabs more intuitive, pragmatic and simplified in Camera Raw. Texture, Clarity and Dehaze tools shouldn’t be recognized as effects. These tools are pretty much just another contrast sliders using different algorithms. That is why these tools should be moved to the Light tab.What should be in Effects tab is Vignette, Grain and Lens Blur.Lens Blur as a tab should be removed and moved into Effects tab as a new tool.Effects tab to be dropped to the second tab from the bottom as it would become one of the least used tabs after the update.  Masking Menu: In the Masking menu Light tab should be the same as the main menu containing Texture, Clarity and Dehaze. Effects tab to be completely removed. The Grain tool to be moved into Detail tab. Detail tab in Masking menu could be renamed to ‘Details’ because it would contain slightly different tools from the main menu tab called ‘Detail’. It is to avoid confusion and teach users that Detail and Details tabs are different in the main menu and Masking menu. Thank you. 

0
daring_Cascade3810
Forum|Forum|6 months ago
Delightful_Rainbow8388
Delightful_Rainbow8388Participant

Layer shortcut keyOpen for Voting

In my project, adding layer masks, applying filter effects and adjusting the color levels are very frequent actions. Could we add custom shortcuts only within the layers?If it's customizable, please let me know. Thank you.

0
Delightful_Rainbow8388
Forum|Forum|6 months ago
marta_feriani_scl
marta_feriani_sclParticipant

Support paths > 260 characters on WindowsOpen for Voting

Current builds of Substance Painter 3D on Windows do not support handling paths longer than 260 characters (Windows MAX_PATH limit). Starting with Windows 10, version 1607, MAX_PATH limitation can be lifted. However, this is an opt-in behaviour applications must explicitly subscribe to. https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later Could future builds of Substance Painter 3D implement this new Windows feature, thus removing the limit on paths length? Thank you ⭐

1
Cyril Dellenbach
Forum|Forum|6 months ago
FeedbackCommunityMemberInspiring

Change default "Show Clip Keyframe" for entire sequenceOpen for Voting

The visible keyframe slider for every video is Opacity by default. It is a nightmare trying to right click each clip, if you need to display a different keyframe for it (E.g. Time for speed ramps).An option is necessary for setting the default displayed keyframes for the entire sequence. The ability to also bulk change thedisplayed keyframes for multiple clips would also be good.

27
Forum|Forum|6 months ago
alexandred28031804
alexandred28031804Participant

Inconsistent audio behavior in Source Monitor with multicam sequences (audio duplication / unintended mixdown)Open for Voting

Since at least Premiere Pro 2023 (still present in 2026), the Source Monitor does not correctly reflect the actual audio structure of multi-cameras sequences when external audio sources are used. Context:The issue occurs with a multicam sequence built from: Two camera angles (camera audio disabled or ignored) Two external mono audio sources (MIC1 and MIC2) Synchronization performed using In points (clap) Inside the multi-camera sequence (timeline), the audio behaves correctly : MIC1 and MIC2 are properly separated Each microphone is on its own track Playback is correct  Expected behavior :When opening the multi-camera sequence (or a derived target sequence) in the Source Monitor: Audio tracks should remain distinct (MIC1 different from MIC2) Waveforms should reflect the actual content of each track Inserting into another sequence should preserve separate audio tracks without duplication or mixdown Observed behavior, in Source Monitor : All audio waveforms become identical Only one audio source (e.g. MIC2) is effectively used across all tracks Inserting into a sequence results in duplicated audio instead of separate tracks This behavior is inconsistent with the same sequence when opened in the timeline, where audio remains correct. Additional notes : The issue persists after: Recreating the multi-camera sequence from scratch Verifying audio channel mapping Using mono and standard tracks The problem appears to be related to how Premiere interprets a multicam sequence as a source clip It behaves like an unintended mixdown or remapping inside the Source Monitor Impact : Prevents proper multi-camera logging (derushing) with multi-track audio Breaks professional interview workflows using multiple microphones Forces inefficient workarounds (copying from timeline, disabling audio, etc.) Results in significant time loss Comparison:In Avid Media Composer, audio and video inserted from a source (clip or sequence) preserve : Track structure Channel separation The Source Monitor reflects the actual content reliably.  Conclusion:In Adobe Premiere, the Source Monitor does not preserve the audio integrity of multi-camera sequences, leading to duplication or unintended mixdown of audio tracks. This is both a functional issue and a significant UX problem for professional workflows. 

1
R Neil Haugen
Forum|Forum|6 months ago
Zachary5DCBParticipant

Photoshop Needs an Update/Refresh to its Interfaces and RoutinesOpen for Voting

I have been working with Adobe Photoshop (Illustrator, After Effects & Premiere Pro as well) for ~20 years. And over the last five it is a little curious to see so many updates to filters, generative tools, and advanced selection tools and almost literally nothing else. I like these changes and updates, don't get me wrong. But the basic workflow of the app feels positively archaic in 2025. A good example of a the kinds of circular and needlessly complicated routines PS still requires here: An example of a brutally segmented task that many people are familiar with below. It's something that sometimes I'll do from habit without thinking about. But when I think about it, it's absurd.The math that compels a pixel selection -> path -> shape is right there and should be controllable with a two click operation, and one click in any one direction creating a real-time layer (not a saved custom shape that requires more tedious menu diving or a path in a paths tab that visually corresponds to nothing and requires more separate steps to create something graphically meaningful). 1. Make a selection: Select the pixels within the raster mask you want to convert. You can do this by holding Ctrl (Windows) or Cmd (Mac) and clicking the layer thumbnail in the Layers panel.2. Convert the selection to a path: Go to the Paths panel (Window > Paths) and click the Make Work Path icon (a dotted circle) at the bottom. You may need to adjust the tolerance for best results. 3. Make sure the path is selected: In the Paths panel, make sure the path you just created is selected.4. Convert path to shape: In the options bar at the top, click the Shape button. This will create a new shape layer with the path as its vector mask 5.5. Fill the shape: With the new shape layer selected, choose a solid color fill from the Layers panel menu (Layer > New Fill Layer)Other examples of out-of-date interfaces that could use a refresh.1.) Anything related to color range selections and/or legacy filters that propagate into useless postage stamp-like windows that we are supposed to use as a preview.2.) And save-for-web style menu options with cluttered Windows 3.1 style interfaces.Still enjoy the products professionally but consider some updates like this focused on modern usability.

2
jane-e
Forum|Forum|6 months ago
Youenn DenisParticipant

Lock on the transform matrixOpen for Voting

Currently, the only way to prevent accidental spatial movement of a layer is to use the global "Layer Lock." However, this prevents all other interactions (trimming, adding effects, color grading, or adjusting masks).In workflows like conforming, color grading, or technical compositing, we often need to ensure a layer remains at its exact coordinates without freezing the entire layer. A simple accidental press of an arrow key or a "click-and-drag" in the Composition window can create sub-pixel shifts or black edges that are hard to spot until the final QC.Proposed Solution Individual Property Locking: Add a "lock" icon next to the Transform group in the Timeline. Clicking it would disable any spatial changes (Position, Scale, Rotation, Anchor Point) while keeping the layer selectable and editable for effects. Visual Indicator: A small lock icon visible next to the "Transform" text when the layer is unrolled. Preferences: Add a setting in Preferences > General to "Auto-lock Transform for new layers" for specific project types. Keyboard Shortcut: A toggle command to quickly lock/unlock the transformation matrix of selected layers. Why this mattersThe current workaround involves writing expressions to "freeze" properties, which is time-consuming and cluttering. Native transform locking would significantly "solidify" the software for professional high-stakes deliveries and prevent costly human errors.

2
Forum|Forum|6 months ago
gethoInspiring

Bridge-like metadata selection on thumbnailsOpen for Voting

Freeform view allows you 2 lines of metadata, but has no ability to sortThumbnail view is antiquated, needs more info!  Allow metadata display similar to bridge  eg label by preferably colouring the frame with the label colour (like lightroom), and giving us the ability to add eg video info below the thumbnail (with a quick toggle button or shortcut like lightroom where you can quickly get back to a clean view)and then have the ability to sort or filter by the items displayed.    

0
Forum|Forum|6 months ago
Eframe JohnParticipant

Colored Labels in Icon ViewOpen for Voting

Is there a way to show colored labels on Icon View? I'm seeing the labels on Thumbnail View and Freeform View but not in Icon View. It's easier to see label groups even in Icon View for faster search. If there is no such thing, I think this would be helpful for others too.

3
Forum|Forum|6 months ago
luxBorealis
luxBorealisInspiring

P: Offer AI Denoise in the cloud so that Lightroom for iPad users could access it.Open for Voting

iPad has become my default device for editing in Lightroom. Since Denoise was introduced, though, iPad has become less useful to me until files have been denoised.Having denoise occur in the cloud would solve this issue. Adding other processes to the cloud such as Merge and Generative Upscale would make iPad even more useful for editing with Lightroom.

0
luxBorealis
Forum|Forum|6 months ago
paulf2020
paulf2020Participant

Generative AI Fill for Warp Stabilizer Border Edges (Firefly-Powered Content Generation to Eliminate Black Borders)Open for Voting

Problem: Warp Stabilizer in Premiere Pro often introduces black borders/edges due to frame shifting and warping, especially on dynamic handheld footage (e.g., golf swings, walk-and-talk conversations, cart shots in sports docuseries). Current options like "Stabilize, Synthesize Edges" use basic frame blending/extrapolation and frequently fail on complex motion/content, forcing workarounds: manual nesting + scaling/cropping, Auto Reframe, or roundtrips to DaVinci Resolve for better stabilization/edge handling.Requested Feature: Integrate a true generative AI option (powered by Adobe Firefly, similar to Generative Extend for clip extensions) directly in Warp Stabilizer's Borders section—or as a follow-up AI effect. This would analyze surrounding frames/content and intelligently generate plausible fill for black edges, preserving full frame composition without cropping, softening, or losing resolution. Options could include: - Strength/quality sliders (e.g., low/med/high generation fidelity) - Prompt guidance for specific content (e.g., "extend green grass and sky") - Preview toggle before apply - Batch/process across clipsWhy this matters: For performance-driven content like my Golf series, stabilization is essential for cinematic quality without losing edges on rotational/impact shots. This would streamline DIT-to-Premiere workflows, reduce manual fixes, and align with Premiere's AI evolution (Generative Extend, Text-Based Editing, etc.).Workflow example: Stabilize clip → Enable "Generate Fill" in Borders → AI fills edges seamlessly → Export clean timeline. Thanks for considering—this would be a game-changer for sports/documentary editors!

1
Peru Bob
Forum|Forum|6 months ago
justinou11
justinou11Participant

P: Mobile side by side photo comparisonOpen for Voting

I’d like to compare 2 photos side by side in Lightroom Mobile (on iPhone), but there’s no way to do that. Also, when you swipe from one photo to another, it would be great to have an option that if you click on the side instead of swiping, you go to the next photo without a transition, which would do the same as clicking your keyboard’s arrow on PC. HashPhotos (a free app) has already did that, so I think it’s just natural that Lightroom, at the cost people pay to use it, adds the feature. It would greatly help comparing photos effectively.

0
justinou11
Forum|Forum|6 months ago
johnrellis
johnrellisLegend

Photoshop: Providing PSB/PSD thumbnails and previews for OS XOpen for Voting

SummaryAdobe can provide fast, high-quality thumbnails and previews of PSD and PSB files to the Mac Finder at low engineering cost and without any involvement from Apple. There are two independent improvements:- Store higher-resolution JPEG previews in PSD and PSB files.- Implement an OS X Quick Look Plugin for handling PSD and PSB files.Storing higher-resolution previews would eliminate the need for users to save files with the Maximize Compatibility option just to get larger thumbnails and previews in the Mac Finder and Windows File Explorer. It would also speed up the generation of thumbnails and previews for very large files (hundreds of megabytes and larger). Previous versions of Photoshop stored such previews, but this functionality was removed some number of versions ago.Implementing a Quick Look plugin would provide thumbnails and previews of PSB files (not currently provided on OS X), and it would greatly speed up previewing very large PSD files. It’s quite straightforward – many third-party developers do it, it is well-supported by Apple, and I managed to do it without any prior programming experience in OS X or Photoshop.The rest of this post explains the proposal in more detail.Higher-Resolution JPEG PreviewsWhen you select the Image Previews: Windows Thumbnail save option, Photoshop CC 2014 stores a 160x160-pixel JPEG thumbnail in the PSD/PSB file. (The Icon option does nothing, by the way.) The OS X 10.9/10.10 built-in Quick Look functionality (invoked by the Finder) uses that JPEG, if present, to generate thumbnails 192x192 and smaller. If the JPEG thumbnail is not present, or if it is present but the Finder requests a size larger than 192x192, then Quick Look will make a thumbnail using the composite image stored by the Maximize Compatibility option.There are two problems caused by the small size of the thumbnail:- Generating a larger-size thumbnail from the composite image can take a very long time. For example, with a 1.3 GB PSD file stored on an SSD on my 2014 Macbook Pro 15” (2.6 GHz i7), it takes the Finder 13 seconds to produce a 512x512 thumbnail or a 2000x2000 preview, whereas it takes just 0.1 seconds to produce a 192x192 thumbnail. If the Finder handled PSB files using the same method, it would take about 130 seconds to generate thumbnails for a 13 GB 100Kx100K PSB.- If the Maximize Compatibility option isn’t set and there are two or more layers in the file, then the composite image will be missing, and the Finder will show a blank thumbnail and preview. Many users resist saving with Maximize Compatibility because it can increase the file size by a fair bit (by storing an additional full-resolution layer), and such users get blank thumbnails and previews.If Photoshop stored a higher-resolution JPEG preview, say 2000x1333, it would allow the current built-in Quick Look generator to provide larger Finder thumbnails extremely fast, even for very large files. It would also allow users to save their files without Maximize Compatibility but still see thumbnails up to the Finder’s maximum of 512x512.High-resolution JPEG previews would also enable very fast Finder previews, even without Maximize Compatibility. The current Quick Look generator doesn’t use the JPEG previews for generating Finder previews, but a generator plugin written by Adobe (see the next section) could easily do so.Previous versions of Photoshop used to store higher-resolution previews in PSD/PSB files. In fact, the current Photoshop CC 2014 documentation still (incorrectly) describes the Full Size option for saving 72-ppi previews.The high-resolution preview would add proportionately very little to the file size. A 2000x1333 medium-quality (6) preview, suitable for large Finder previews, takes on the order of 625 KB.There are two options for where to store the high-resolution JPEG in the file format. Photoshop could simply increase the size of the current thumbnail from160x160 to 2000x2000 and continue to store the JPEG in image resource block id 1036. The publicly available specification for PSD/PSB files puts no limit on the size of JPEGs stored in that block.Alternatively, if Adobe is concerned about compatibility with software that incorrectly assumes that the JPEG in block 1036 is 160x160, it could introduce a new image resource block to store the high-resolution preview. It could resurrect the Image Preview: Full Size option to control whether the high-resolution previews are actually created.Regarding compatibility, I’ve successfully tested the following applications with a PSD file containing a 2000x1333 JPEG preview stored in the existing image resource block 1036:- OS X 10.9/10.10 Finder/Quick Look- Ardfry’s PSD Codec (Windows)- Bridge CC (OS X)- PSB Quick Look (my Quick Look plugin)Implementing an OS X Quick Look Plugin for PSD/PSBThe OS X Quick Look facility lets Finder, open/save dialogs, and other applications show thumbnails and previews for any file type. Quick Look has built-in the ability to preview the most common file types: PDF, JPEG, text, etc. While it can preview PSDs, it doesn’t handle PSBs, even though the two file formats are nearly identical.However, Apple defined the Quick Look architecture to make it easy for application developers to add previews for additional file types. The developer provides a Quick Look plugin (or “generator”) that reads files of a given type and generates the previews. The plugin architecture is well-supported by Apple, with reasonable documentation and templates in the Xcode development tool. Many, many applications provide their own Quick Look plugins to enable their file formats to be previewed.It’s very straightforward to write a Quick Look plugin. Having no experience with OS X programming or Photoshop file formats, I was able to implement my PSB Quick Look plugin in less than two weeks. The plugin relies on an unencumbered open-source library, ImageMagick, to read the contents of PSD/PSB files, with about 350 lines of new C code as “glue” between Quick Look and the library.It would be similarly straightforward for Adobe to implement a Quick Look plugin for PSD/PSB files. Adobe could use its own internal libraries to read PSD/PSB files, which would likely be even faster than the ImageMagick libraries. (For example, Adobe Bridge generates thumbnails and previews for PSD/PSB files very quickly.) Adobe would just need to write the few hundred lines of glue code between Quick Look and their library. Note that a vendor-provided plugin can override the previewing built-in by Apple, so Adobe’s PSD plugin could override the one built-in to OS X.Adobe and Apple seem to be in a finger-pointing contest about who takes responsibility for writing a PSB plugin. Apple’s position is reasonable—they build in the most commonly used file formats and expect application developers to provide the rest. PSBs are not used as widely as PSDs, so Apple expects Adobe to provide the plugin, and that clearly annoys Adobe. But other application developers have to write their own Quick Look plugins, so why doesn’t Adobe? Given the low cost of building a plugin, Adobe’s refusal makes them look petty and unconcerned about its customers.Some design considerations of a PSB/PSD Quick Look plugin:Given modern cameras, HDR, panoramas, and multi-layer editing, PSD and PSB files are getting very large, ranging from hundreds of megabytes to tens of gigabytes. So it’s important that a plugin avoid reading the entire file just to produce a small thumbnail or preview.If Photoshop stored a higher-resolution JPEG preview in the file, as proposed above, then it’s very easy for the Quick Look plugin to provide a thumbnail or preview quickly. The plugin just seeks to the right location in the file and reads out the relatively small JPEG preview. (This is what the Apple PSD plugin and my PSB/PSD plugin do to access the stored thumbnail.)But if Adobe chooses not to store higher-resolution previews, it’s still straightforward for the plugin to produce thumbnails and previews reasonably quickly. The plugin doesn’t read the entire composite image (stored by the Maximize Compatibility option), only a down-sampled subset of the rows of the composite. For example, suppose a PSB file stores a 300K x 300K image, and the plugin needs to produce a 500 x 500 thumbnail. The plugin would read just 1000 rows from the composite image, rather than all 300K rows, reducing the total I/O by 1/300. The plugin would then down-sample that 1000x1000 image to 500x500 using a fast but mediocre-quality resize algorithm.My PSB plugin uses this down-sampling strategy, and it’s able to preview a 10 GB PSB file in a couple of seconds. It took about 20 extra lines of code in the open-source image library to implement.

9
erickeee
Forum|Forum|6 months ago
ProBee
ProBeeParticipant

[FEATURE REQUEST] Add "Maintain Independent Anchor Point" Option for Camera ParentingOpen for Voting

Currently, in After Effects, when a Camera is parented to a Null object, its rotation axis is forcibly overridden by the Null's anchor point. This makes complex camera movements (like orbiting and panning simultaneously) extremely counter-intuitive and difficult to control.Please consider adding a toggle or option to "Maintain Individual Axis" when parenting cameras. This would allow the camera to follow the Null's position while retaining its own rotation center, similar to how modern 3D engines or Cinema 4D handles parent-child transformations.For motion designers and AMV editors working with complex 3D space, the current workaround (using multiple Nulls or complex expressions) is a significant bottleneck in the workflow.Thanks  

1
jane-e
Forum|Forum|6 months ago
AndrewFloresParticipating Frequently

Project Sound LiftOpen for Voting

Please release Project Sound Lift for Speaker Diarization. I would Greatly Appreciate it! It would allow me to edit videos 100X’s fast no exaggeration!! 

1
Forum|Forum|6 months ago
NotPhilSledge
NotPhilSledgeParticipant

I would love to see an integration between Adobe Firefly and OpenClawOpen for Voting

I would love to see an integration between Adobe Firefly and OpenClaw to allow creators to send prompts, generated images, or assets directly between the two platforms. This would make it easier to incorporate Firefly-generated visuals into automated workflows and AI-driven creative tools. For example, creators could generate images in Firefly and automatically send them to OpenClaw for further processing, automation, or integration into other creative pipelines. This would help creators build more advanced AI-assisted workflows while keeping Adobe Firefly at the center of the creative process.

1
Kartika Rawat
Forum|Forum|6 months ago
PBJM Studios
PBJM StudiosInspiring

Give Firefly a Bigger Brain: Support Attached Instruction DocumentsOpen for Voting

Here is my idea….Feature Request: Allow Uploading a PDF/DOCX as Structured Instructions for FireflySummaryToday, Firefly prompts are constrained to a relatively short text length (community and staff discussions have historically referenced ~1,000 characters, with users sometimes encountering lower effective limits depending on the model or surface). This makes it hard to use Firefly’s recommended, structured instructions without aggressive pruning—reducing clarity and, ultimately, output quality. What I’m asking forPlease add a capability to attach a reference document (PDF or DOCX) to a generation request so Firefly can read and follow a structured instruction sheet in addition to a short prompt. This mirrors the research-and-attach flow I use elsewhere (e.g., Copilot scenarios where I attach a brief or template), and would let the short prompt act as a high‑level instruction while the document carries the detailed guidance.Why this mattersStructured prompts drive better results. Adobe’s own guidance encourages clear structure (subject, style, lighting, camera, etc.), but fitting that rigor into a tight character budget forces users to drop essential detail. A referenced document would preserve intent and nuance without breaking the UI’s brevity. [community.adobe.com] Consistency across assets. While Firefly supports reference images (and even 3D scenes) to guide style/pose/composition, there is currently no way to attach a textual brief that governs instructions across scenes and shots. Document attachments would complement image/scene references, not replace them. [helpx.adobe.com], [adobe.com], [helpx.adobe.com] Creative workflows already use briefs. Teams typically work from brand/episode templates and production notes; enabling Firefly to consume these directly would reduce iteration cycles and errors.Proposed user experience (UX)In Text‑to‑Image or Text‑to‑Video, add an “Attach instructions (PDF/DOCX)” control next to the prompt. Firefly ingests the document at generation time and treats it as authoritative guidance. The short prompt still exists for quick overrides (e.g., “Scene 3 variation: closer framing”). A toggle lets users choose priority: Prompt > Document or Document > Prompt.Acceptable formats and scopePDF and DOCX up to a practical size limit (e.g., 2–5 MB). Read only text content; ignore embedded media unless future versions support it. Respect existing content and safety filters; if the document includes disallowed directives, Firefly should flag them before generation.Example of the type of document to attach(This is the structured template we use for kids’ content; Firefly would read it as persistent guidance across shots.)Adobe Firefly Standard Instructions Template.Follow these instructions precisely:Audience/Purpose: [insert]Subject/Scene: [insert]Style/Tone: [insert]Composition/Camera: [insert]Colour/Lighting: [insert]Fidelity/Output: [insert]Do not add extra elements beyond what is listed.[business.adobe.com]Benefits to Adobe and usersHigher satisfaction and fidelity: clearer inputs → fewer retries → stronger trust in Firefly. Enterprise readiness: teams can standardize briefs and enforce brand/story rules at scale. Bridges current gap between concise prompts and real production requirements.ClosingFirefly already embraces reference images and 3D scene references—document references are the natural next step for instructional fidelity. Please consider enabling PDF/DOCX attachments so we can maintain clarity, consistency, and safety without fighting character limits. [helpx.adobe.com], [adobe.com], [helpx.adobe.com]

1
Kartika Rawat
Forum|Forum|6 months ago
Admirable_joy5ECC
Admirable_joy5ECCParticipant

canvas-based editor with a node systemOpen for Voting

Dear Adobe team,If you have truly decided to focus on the AI segment and are no longer giving the same level of attention to Illustrator, XD, and other products, then please make Firefly’s interface genuinely convenient and professional.In my view, what you need most right now is a proper canvas-based editor with a node system. That would be a far more powerful and logical format for working with generative tools. As a reference, Weavy is a very good example of this kind of approach.In your case, however, this should not be just another web service — it should be a full desktop application deeply integrated into the Adobe ecosystem. Most importantly, it should allow generated results to be passed easily into After Effects, Photoshop, and Illustrator, creating the kind of seamless workflow that users expect from Adobe products.If you build it this way, you could end up with a truly outstanding product for professionals. And for users, it would mean being able to stay within a single ecosystem instead of constantly learning alternatives and stitching together workflows from disconnected tools.

1
Kartika Rawat
Forum|Forum|6 months ago
default7ty7cxqhx5hrParticipant

enable a dolly zoom or a camera spin to a locked off shot for uploaded videoOpen for Voting

I'd wish you could upload existing video clips to Firefly so you could add camera motion to shots. For example, adding a dolly zoom or a camera spin to a locked off shot.I’d like to be able to add difficult to execute camera motion to the footage I shot. So if I have a locked off shot of someone standing in a kitchen holding the snack product I am creating a video for, I would like to be able to use AI to add dramatic camera motion to the otherwise boring shot. I’d like to be able to add camera movements like a dolly zoom as the person takes a bite, or add a camera spin around the person as they enjoy the snack.

1
Hajar Toutsi
Forum|Forum|6 months ago
Show more posts

Filter by product

  • All products
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices