Best Claude Code plugins for ecommerce product image & video (2026)

For image-heavy Claude Code work, pick hex/claude-image-generation. WaveSpeed is the broadest one-stop integration for teams that need image, video, audio, and 3D from a single CLI. If your stack is Google-only, visualgen-mcp is the clean route to Imagen 4 and Veo 3.1. Remotion sits apart: it renders repeatable MP4s from React; it does not synthesize footage.

Treating “media generation” as one buying decision is the mistake. A PDP team revising a packshot across Gemini, OpenAI GPT Image, and xAI Grok Image needs something very different from a social team stitching together music, lip sync, clips, captions, and delivery files. Anthropic’s plugin directory describes Claude Code plugins as installable bundles of tools, skills, and integrations. Buy for the production constraint, not the flashiest model roster.

The usable shortlist has seven tools: hex/claude-image-generation, WaveSpeed, visualgen-mcp, Pexo, Higgsfield, Claude Video, and the Claude Code Video Toolkit. They cover four distinct jobs: still-image creation and editing, model-generated clips, multi-shot production, and deterministic programmatic video. That division should shape a short paid pilot.

What is the best Claude Code plugin for AI product images?

hex/claude-image-generation is the best documented option for teams making and revising product images inside Claude Code. At runtime, it supports Google Gemini, OpenAI GPT Image, and xAI Grok Image. A developer can keep the prompt and reference inputs fixed, swap image providers, and avoid rebuilding the workflow around each API.

Its catalog-work features are unusually useful. Text-to-image handles new scene concepts. Text-guided editing works from an approved base frame; multi-image input can take product, packaging, logo, and visual-reference files together; parallel generation gives an art director several options in one review pass. Inline and tmux previews matter too: the instruction writer sees the output beside the prompt, asset path, and revision request.

Use hex when provider choice is part of the job. A cosmetics SKU may need a clean studio treatment from one provider and a more editorial setting from another. The project documentation does not publish a starting subscription price. Price the whole path: enabled APIs, generation volume, review time, and approved variants—not the plugin install alone.

Which plugin gives Claude Code the broadest media coverage?

WaveSpeed is the best documented choice when one Claude Code integration needs to reach image, video, audio, and 3D generation. Its official marketplace plugin runs through the WaveSpeed CLI. You can use the same capability as a skill or through an MCP server.

That range changes the build for a small creative-automation team. Instead of wiring separate interfaces for a still image, motion clip, audio element, and 3D asset, the team can set up one account and one command-line entry point, then layer project-specific instructions over it. WaveSpeed needs a CLI plus an API key or login. Put credential handling and API spend into the initial repository setup.

Breadth does not equal a finished campaign workflow. Run one actual brief through it: a named SKU, reference image, required aspect ratio, product copy, and delivery folder. Check fidelity in the first image and the final video frame, then see how easily the CLI output reaches the person approving creative.

Is visualgen-mcp right for Imagen 4 and Veo 3.1?

visualgen-mcp is the direct pick for a Claude Code workflow committed to Google’s Imagen 4 for stills and Veo 3.1 for short video. It exposes both through Google’s Gemini API and writes generated files into the active project directory.

Its split image and video interfaces make sense in practice. Image generation is synchronous, suited to a prompt-and-review loop for a background swap, product composition, or concept board. Video runs as an asynchronous submitted job and is then polled, closer to an actual production flow: Claude Code can hold the job state, gather the finished file, and feed its file path into downstream editing or approval instructions.

This is a focused tool rather than a provider switchboard. Pick it when Imagen 4 and Veo 3.1 are deliberate platform decisions and project-local file output matters. Teams planning to test Google, OpenAI, and xAI images against the same brief will find the documented hex/claude-image-generation feature set more relevant.

What should you use for multi-shot AI video production?

Pexo is the list’s most explicitly multi-shot-oriented option. Still, validate its positioning in a paid production test before standardizing. Pexo describes a Claude Code skill that routes across more than 10 models and combines AI music, lip sync, sequencing, and multi-shot video production.

That package tackles what a single generated clip leaves undone: a sequence with a beginning, product reveal, claim, close, sound, and continuity between cuts. Pexo also describes an image-to-video workflow that takes multiple images through to a finished multi-shot video. Those are vendor descriptions. Test the ecommerce failure points: repeated product label text, logo geometry, hands near the product, exact color, and the final 9:16 or 16:9 crop.

Higgsfield is the sharper candidate when the recurring issue is keeping a recognizable person or character across shots. Pexo’s comparison specifically positions Higgsfield’s Soul ID around character consistency. That alone does not settle a product-first spot. A bottle, sneaker, or box still needs close review for packaging and material continuity.

Why is AI video harder than AI image generation?

AI video is harder because each frame has to agree with the ones around it, while motion, camera movement, lighting, product geometry, and audio add failure points. A still gets approved as one image. A 12-second clip has to survive playback, cuts, captions, crop changes, and its final frame.

George Liu’s observation is the right rule for anyone building a Claude Code media workflow: move from a still-image proof to a video pilot with narrower expectations, tighter review checkpoints, and an explicit post-production path. Test one simple shot before commissioning a six-shot narrative. Keep product reference images and approved visual constraints beside the prompt; do not rely on a broad description remembered from earlier.

When should you use deterministic video over generated footage?

Use Remotion through the Claude Code Video Toolkit when you need a repeatable, code-defined motion graphic instead of a synthetic filmed scene. The toolkit describes React components rendered to MP4, along with Manim, screen recording, clipping, and FFmpeg post-processing.

This is the right lane for price cards, product-comparison animations, launch countdowns, localized end frames, changelog clips, and any format where a legal line or SKU name has to land in the exact same place every time. A React component can take a product name, image path, price, locale, and duration as inputs. The render produces a predictable file rather than asking a generative model to redraw text frame by frame.

Remotion does not replace Veo-style footage. It is the reliable finishing system around it. Use model-generated video where believable material, styling, people, or movement are required. Keep typography, product cards, captions, and versioned layouts in code-defined rendering, where they should not drift.

Which Claude Code tool handles editing, captions, and delivery?

Claude Video is the best fit on this shortlist for terminal-oriented editing and delivery around generated media. Its documented suite includes video editing, transcoding, captioning, analysis, audio processing, short-form conversion, stock-footage promo workflows, image generation for video assets, and Veo 3.x text-to-video.

Claude Video earns its place after the generation choice, when a team has to turn a master into platform variants. A generated product clip may need captioned vertical output for a social placement, another duration for an ad unit, a publisher transcode, and a quick speech or scene-content check. Keeping that work in the same Claude Code project cuts file hunting and makes output conventions easier to document.

Do not mistake post-production range for an independent visual-quality claim. Test the editing path on work you already make: import a short generated clip, create captions, cut a vertical version, process audio, and inspect the delivered file on its destination platform.

What is the practical recommendation for ecommerce and creative teams?

Start with hex/claude-image-generation for on-brand product-image iteration. Add WaveSpeed only when broad media access is an actual operating need, not a future maybe. Teams standardized on Google APIs get the most direct Imagen 4 and Veo 3.1 pairing from visualgen-mcp. For exact title cards and repeatable product animations, use Remotion through the Claude Code Video Toolkit.

For a larger video workflow, split generation and finishing deliberately. Pexo is the candidate for a multi-shot experiment; Higgsfield merits testing when a persistent character drives the work; Claude Video is the candidate for captions, conversion, editing, and delivery. Each one clears a different bottleneck.

Run the pilot on a brand-critical, bounded asset: one SKU, one audience, one channel, and two approved visual references. Choose the setup that preserves the product, meets the delivery specification, and gives the creative team enough iterations to select from—not the setup with the most impressive first clip.

Frequently asked questions on Claude Code media plugins

Which Claude Code plugin is best for image editing? hex/claude-image-generation is the strongest documented image-editing choice. It supports text-guided edits, multi-image input, parallel generation, and runtime selection among Gemini, OpenAI GPT Image, and xAI Grok Image.

Can Claude Code generate images and video through one integration? Yes. WaveSpeed documents image, video, audio, and 3D generation through its Claude Code marketplace plugin and CLI. visualgen-mcp pairs Imagen 4 images with Veo 3.1 short videos through the Gemini API.

What is best for programmatic product videos? The Claude Code Video Toolkit best suits deterministic layouts because it uses Remotion React components rendered to MP4. Use it for repeatable product cards, captions, pricing animations, and localized end frames rather than synthetic footage.

Do Pexo and Higgsfield have independently proven rankings? No single independent benchmark is identified here. Pexo’s multi-shot and model-routing claims, along with its characterization of Higgsfield’s Soul ID, come from Pexo’s own vendor comparison. Run a paid test on your actual brief before making a long-term commitment.