Feature Requests

Feature Request: Batch Export to Google Drive via Agent Underlord Summary: Add the ability for Agent Underlord (the AI assistant) to programmatically trigger exports to Google Drive, including batch exports of multiple compositions at once. Current Limitation: The export_video tool available to Agent Underlord can only export compositions as MP4 to the user's local computer. It has no support for third-party destinations such as Google Drive, YouTube, or any other publishing integrations. When a user asks the agent to "export to Google Drive," the agent is forced to decline and redirect the user to do it manually — one composition at a time — through the Export dialog. The Problem This Creates: Users who manage multiple compositions (e.g., a YouTube version, a regular version, a members-only version, and multiple short-form clips) must manually open each composition, navigate to Export, authenticate with Google, and trigger each export individually. This is time-consuming and repetitive, especially for creators with regular publishing workflows. Requested Behavior: * Allow Agent Underlord to export one or more compositions directly to Google Drive (or other supported destinations like YouTube) * Support batch exports: accept a list of composition names or IDs and export all of them in sequence * Optionally allow specifying resolution, destination folder within Google Drive, and file naming ⠀ Use Case: A creator finishes editing 7 compositions (YouTube cut, regular cut, members cut, 3 shorts, and an ad) and asks the agent: "Export all of these to Google Drive." The agent should be able to handle this entirely without requiring manual intervention for each file. Impact: High — this would save significant time for any creator managing multiple output formats or publishing to Google Drive as part of their regular workflow.

Feature Request: Add Audio-Only Export Support to the export_video Agent Tool Summary: The Agent Underlord AI assistant currently has access to a tool called export_video that can trigger local exports of compositions. However, this tool is limited to MP4 video exports only — it has no parameter for selecting the output format (e.g., MP3, WAV, AAC) or for specifying an audio-only export. Current Behavior: When asking Agent Underlord to export a composition as audio-only, it cannot fulfill the request programmatically. The export_video tool only supports video (MP4) exports. There is no format, audioOnly, or equivalent parameter available in the tool's schema. Requested Behavior: Add an audioOnly boolean parameter (or a format parameter supporting values like mp3, wav, aac, mp4) to the export_video tool so Agent Underlord can trigger audio-only local exports on behalf of the user. Use Case: Podcast producers and video creators who produce both a video version and an audio-only version of their content (e.g., YouTube video + podcast feed) need to export multiple compositions in audio format regularly. Being able to say "export these 3 compositions as MP3" and have the agent handle it would save significant manual effort — especially when managing multiple compositions per episode (e.g., a YouTube cut, a members cut, and an ad spot). Impact: Without this capability, users must manually open each composition, navigate to Export, and change the format settings every time — defeating the purpose of having an AI assistant that can automate repetitive tasks.

Fix need to repeatedly re-connect Google Drive. Add option to export to sub-folder within Google Drive.

Right now when you output a short video, there is no way to keep the font used for captions. When you download the video, the font doesn't always remain the same. Instead you don't get the font you've selected. Can you create a toggle to allow the font to be baked in or allow the font file to be embedded into the file?

I don't use the web version of Descript and the desktop version used to have the export to YouTube functionality, but for a long time it has said that the feature is coming soon. I don't understand why it was removed in the first place. It seems to me the web version and the desktop version should be identical in features. I post 40+ videos per month to YouTube and it's a pain to export to local and then upload to YouTube, not to mention the drain on my physical resources.

Want to integrate descript into production workflow (i.e export from an API / trigger) so that we can automate the production of videos with subtitles.

Descript version: 139.0.19 OS: Windows Project type: Video, Portrait 9:16 (1080×1920) Bug description: All portrait compositions export as 1280×720 landscape regardless of composition orientation settings. The canvas preview correctly shows portrait layout, and layer/composition properties confirm 1080×1920, but the exported MP4 is always 1280×720. Steps to reproduce: Create a new composition, set orientation to Portrait (1080×1920) Import any portrait video file (tested with 1080×1920 native .mp4 and .mov files) Add video to script track Export as MP4 Output file is 1280×720 landscape Expected result: 1080×1920 portrait MP4 Actual result: 1280×720 landscape MP4 What was ruled out: Not source file metadata — reproduced with multiple portrait sources including a native 1080×1920 .mov with no rotation flags (verified via ffprobe) Not VFR/variable frame rate — reproduced with CFR-encoded sources and non-slo-mo footage Not a single file issue — reproduced across 10+ compositions with different source files Composition orientation is correctly set in UI; canvas preview looks correct Impact: Unable to export any portrait video from Descript on Windows. Affects an entire project (10 compositions). Workaround: None found on Windows. Awaiting test on Mac/web app.

I'd like to request that advanced audio export settings (channels, normalization, bitrate, and sample rate) be made available for cloud export destinations like web links and Google Drive — not just Local Export. Currently, I can only configure mono/stereo channels, LUFS normalization, bitrate, and sample rate when exporting locally. When exporting to cloud destinations, these options are hidden and Descript applies its own defaults. This is a problem for my workflow because: Platform-specific requirements: I produce YouTube mid-roll ad content that requires mono audio normalized to -16 LUFS. Without control over these settings on cloud exports, I can't guarantee my deliverables meet spec. Unreliable internet connectivity: I frequently work on Starlink and mobile connections where upload speeds are inconsistent. Descript's cloud sync and editing work fine on limited bandwidth, but exporting locally and then manually uploading large video files to cloud storage is a significant bottleneck. If I could export directly to Google Drive or a web link with the correct audio settings, I'd eliminate an entire step and a major bandwidth pain point from my workflow. Workflow efficiency: The current workaround — export locally with advanced settings, then manually upload — defeats the purpose of having cloud export destinations in the first place. Bringing advanced settings to all export destinations would make Descript a true end-to-end solution for creators working in bandwidth-constrained environments.

I like the clips made by underlord, but it would be great if we could publish them directly as stories or reals on facebook, instagram, and as shorts on youtube. I'd like to use Descript isted of Opus Clip, but I'm hesitating because of this publishing problem

I have two problems you may not be aware of. 1. When I start the Descript app, it often loads two instances instead of one. I don't click twice, so this is obviously a bug in the software. Nor do I auto-load at startup. Since the last update, whenever I export and download an edited video, it doesn't work. Instead, the wheel spins around and nothing happens. I have to completely re-boot the computer to reset the program and try again. This happens when I save to a web link.