{"id":7918,"date":"2026-06-23T17:31:57","date_gmt":"2026-06-23T09:31:57","guid":{"rendered":"https:\/\/crepal.ai\/blog\/?p=7918"},"modified":"2026-06-23T17:31:59","modified_gmt":"2026-06-23T09:31:59","slug":"palmier-pro-review-ai-video-workflows","status":"publish","type":"post","link":"https:\/\/crepal.ai\/blog\/aivideo\/palmier-pro-review-ai-video-workflows\/","title":{"rendered":"Palmier Pro Review: Honest Pros, Cons & Verdict"},"content":{"rendered":"\n

Hi, I’m Dora. A friend dropped a link in our group chat last week with one line: “an editor where Claude edits your timeline.” Naturally, I went down the rabbit hole. This Palmier Pro review is what came out of it \u2014 though I’ll be straight with you up front: I haven’t run it on my own machine yet, because it’s locked to a very specific setup (more on that in a second). So this is a hands-off breakdown built from Palmier’s docs, the open-source code, and the team’s demos \u2014 not me editing a video at 2 AM. Not sponsored, just honest digging. Here’s what Palmier AI actually is, who it’s for, and the catch nobody’s putting in the headline.<\/p>\n\n\n\n

Palmier Pro Review: The Quick Verdict<\/h2>\n\n\n\n

If you’re skimming, here’s the 30-second version. Palmier Pro is a free, open-source macOS video editor with AI generation built right into the timeline, made by a YC-backed<\/a> two-person team. You generate clips, trim them, and finish the cut in one place instead of bouncing between a generator and Premiere. The big asset: agents like Claude can read and edit your timeline directly. The big catch: it only runs on recent Apple Silicon Macs, and the feature set is bare-bones today.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

Who should look closely<\/h3>\n\n\n\n

Solo creators and small teams already running a generation-heavy AI video workflow \u2014 especially anyone editing alongside Claude, Codex, or Cursor. If your downloads folder is a graveyard of final_v3_actually_final.mp4 files and lost prompts, this was built for your exact pain.<\/p>\n\n\n\n

Who should skip it (for now)<\/h3>\n\n\n\n

Windows and Intel-Mac users \u2014 it simply won’t run. Editors who need color grading, transitions, motion graphics, or effects, since Palmier doesn’t have those yet. And anyone who needs a polished, stable, do-everything editor today instead of an early v0.<\/p>\n\n\n\n

What Palmier Pro Is Built to Do<\/h2>\n\n\n\n

Most AI video tools split your work in two: you generate a clip on the web, download it, then import it into a separate editor \u2014 you become the courier running files back and forth. Palmier collapses that loop. It’s an AI video editor where generation lives on the timeline itself.<\/p>\n\n\n\n

Timeline-first editing with generation baked in<\/h3>\n\n\n\n
\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

Per Palmier’s official docs<\/a>, you pick a model, set resolution, duration, and aspect ratio, and generate a clip straight onto a track. You can lock the first and last frame, add reference images for style or subject consistency, then trim, regenerate, or swap the clip without leaving the project. Here’s the part I actually like: the prompt, model, and references stay attached to each clip. So three days later, when you want to tweak one shot, you’re not digging through a folder trying to remember which prompt made the good take.<\/p>\n\n\n\n

Mixing real and generated footage in one project<\/h3>\n\n\n\n

This is the strongest idea on paper. You import your own footage and drop it on the same multi-track timeline as generated clips. Real B-roll, an AI shot, your voiceover \u2014 one cut, one export. For creators who shoot some footage and fake the rest (most of us now), that’s genuinely useful instead of a gimmick.<\/p>\n\n\n\n

Access, Setup, and the Hardware Catch<\/h2>\n\n\n\n

Here’s the catch I promised. Palmier Pro is macOS-only, built in Swift, and tuned for Apple Silicon \u2014 and it requires macOS 26 (Tahoe) or newer. No Windows. No Linux. No Intel Macs. That one requirement is why I couldn’t test it myself, and it’s the first thing to check before you get excited.<\/p>\n\n\n\n

The good news: the editor is free and needs no login. You can download it and cut video like you would in CapCut \u2014 account-free. AI generation is the paid part. It runs on credits through a subscription, while the editor stays free. Pricing and credit amounts shift with every model update, so check Palmier’s current pricing page before you budget \u2014 I’m not quoting numbers here that could be stale by the time you read this.<\/p>\n\n\n\n

To pull agents in, you enable a local MCP server and connect Claude Desktop, Claude Code, Codex, or Cursor. It’s a one-click install from the app’s Help menu, no account needed for that part either.<\/p>\n\n\n\n

Where Palmier Pro Looks Strong<\/h2>\n\n\n\n

Real timeline control plus in-editor generation<\/h3>\n\n\n\n

A lot of “AI video” tools are slot machines \u2014 type a prompt, pray, download whatever falls out. Palmier reads more like an editor. Generating with frame control, first\/last-frame locking, and reference images means you’re directing shots, not rolling dice. Because it exports to MP4 (H.264, H.265, ProRes) and an NLE XML for Premiere Pro and DaVinci Resolve, adopting it isn’t a one-way door \u2014 you can hand a cut off to a traditional editor for finishing later.<\/p>\n\n\n\n

Agent-assisted editing with full project context<\/h3>\n\n\n\n

This is the headline feature, and it’s a real one. Through the MCP server, Claude or Codex can see your whole timeline and act on it: generate a missing shot, trim dead air, reorder sections, regenerate a clip with a sharper prompt. The editor core and the MCP server are open source under the GPLv3 license<\/a> \u2014 you can read exactly what it does on the public GitHub repo<\/a>. Only the generation pipeline stays closed. For a tool that hands an agent the keys to your project, that kind of transparency matters way more than it sounds.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

Limitations and Trade-Offs to Know<\/h2>\n\n\n\n

Platform and hardware constraints<\/h3>\n\n\n\n

I’ll say it twice because it’s that important: macOS 26 Tahoe, Apple Silicon, nothing else. The app is also early \u2014 version 0.3.5 as of late June 2026 \u2014 so expect rough edges, bugs, and fast-moving changes. This is not a mature, battle-tested editor.<\/p>\n\n\n\n

Models, credits, and generation dependencies<\/h3>\n\n\n\n

Generation runs through third-party models. Palmier integrates the likes of Seedance 2.0, Kling V3, Google’s Veo 3.1<\/a>, Grok Imagine, and Nano Banana Pro for images. That variety is nice, but it also means your output quality, speed, and credit burn all ride on models Palmier doesn’t own. And the honest gap: no color grading, no transitions, no masking, no motion graphics yet. It’s a cutting and generation engine, not a finishing suite. Plan to finish elsewhere.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

Palmier Pro vs Other AI Video Workflows<\/h2>\n\n\n\n

When timeline-first editing fits better<\/h3>\n\n\n\n

If your work is shot-by-shot \u2014 assembling a real cut from real and generated clips \u2014 a timeline beats a chat box every time. This is also where the Premiere Pro AI comparison gets interesting: Palmier’s stated north star is literally Premiere, and the XML handoff means it can feed a Premiere or Resolve finish rather than try to replace it. For editors who already think in tracks and playheads, that’s the natural fit.<\/p>\n\n\n\n

When brief-first direction makes more sense<\/h3>\n\n\n\n

Not every creator wants to touch a timeline. If you’d rather hand over a brief \u2014 a prompt, a PDF, a script \u2014 and let an agent orchestrate the whole video end to end, a brief-first tool like CrePal aims at that job instead: less manual editing, more “describe the outcome and review it.” The two approaches solve different problems. Which one fits comes down to whether you want to direct shots or direct outcomes \u2014 and that comparison deserves its own deep-dive, not a buried paragraph here.<\/p>\n\n\n\n

The Honest Verdict<\/h2>\n\n\n\n

Palmier Pro is one of the more interesting takes on an AI video workflow I’ve seen this year \u2014 not because the generation is magic, but because it fixes the part everyone keeps ignoring: the editing. Putting generation and an agent inside a real timeline is the right instinct, and doing it open-source builds the kind of trust most AI tools skip. But it’s early, narrow, and chained to one platform. If you’re on a recent Apple Silicon Mac and already living inside Claude or Codex, it’s worth a download today. If you’re not, keep it on your radar \u2014 this is a v0 worth watching, not a v1 to bet your whole pipeline on.<\/p>\n\n\n\n

FAQ<\/h2>\n\n\n\n

What timing or sync issues appear when replacing generated clips in the timeline?<\/h3>\n\n\n\n

When working in Palmier AI as an AI video editor, one common issue is duration mismatch during clip replacement \u2014 a regenerated segment may come back slightly longer or shorter than the original, causing downstream audio or cuts to drift out of sync. Many ad video creators solve this by using CrePal first for concept planning, then importing into Palmier AI for precise timeline adjustments, where you can lock first and last frames to maintain better consistency in the overall AI video workflow.<\/p>\n\n\n\n

How should creators decide what to finish in Palmier Pro vs hand off to another editor?<\/h3>\n\n\n\n

A practical rule many creators follow is to handle concept generation and rough assembly in CrePal, then move to Palmier AI for timeline-level control and mixing real footage with generated clips. If the project needs advanced color grading, transitions, or motion graphics, export the XML and hand off to Premiere Pro AI or DaVinci Resolve for final polish. This hybrid approach keeps the strengths of each tool in the right part of the AI video workflow.<\/p>\n\n\n\n

What rights and usage permissions apply to media generated inside Palmier Pro for commercial projects?<\/h3>\n\n\n\n

Since Palmier AI routes generation through third-party models (Veo, Kling, Seedance, etc.), the commercial rights ultimately depend on each model provider\u2019s terms rather than Palmier alone. For client work, most ad video creators treat Palmier AI as part of a larger pipeline with CrePal for planning, then verify licensing at the model level before delivery. Always check the latest official terms, because the rights landscape changes faster than the tools themselves.<\/p>\n\n\n\n

What should teams verify after importing an NLE XML into Premiere Pro or DaVinci Resolve?<\/h3>\n\n\n\n

After exporting from Palmier AI, teams often check relinking (media paths), frame rate consistency, and whether generated clips imported as flat files (losing prompt metadata). A common workflow is to use CrePal for initial concepting, refine in Palmier AI as the AI video editor, then export XML for Premiere Pro AI finishing. This helps catch timing shifts or missing effects early in the AI video workflow.<\/p>\n\n\n\n

Wrapping Up<\/h2>\n\n\n\n

So that’s my Palmier Pro review, hardware catch and all. I genuinely want to test this properly once I’m on a Tahoe machine, because the timeline-plus-agent idea is the first AI editing pitch in a while that made me go “oh \u2014 that’s actually the missing piece.” For now, if you’ve got the right Mac, grab the free editor, wire up Claude through MCP, and run it on a real cut. Then come tell me whether the agent saved you real time or just rearranged the chaos into a neater pile. I’m curious which way it lands.<\/p>\n\n\n\n

\n\n\n\n

Previous posts:<\/strong><\/p>\n\n\n\n

\n
From Codex to Creative Agents for UGC Ads<\/a><\/blockquote>