Skip to content

Need help?

Something not working as expected? You’re in the right place. Pick the category that matches your issue — every page includes step-by-step solutions written for editors, not engineers.

Panel won't open or looks broken

The plugin isn’t showing in Premiere Pro, the panel is blank, or you see “Connection interrupted.” Fix panel issues →

Generation is stuck or failing

Your generation is stuck on “Queued” or “Generating”, the button is disabled, or you’re seeing an error. Fix generation issues →

Media or file error

“Image too small”, “File too large”, 0x0 dimensions, or “No media selected.” Fix media issues →

Model won't load or is missing

“Access denied”, “Could not load”, “Temporarily unavailable”, or incorrect parameters. Fix model issues →

Cost or pricing question

“No price” showing, estimates don’t match actuals, or you want to understand how pricing works. Understand costs →

Server or connectivity problem

Port conflicts, Node.js errors, fal.ai connection issues, or the backend server won’t start. Fix connectivity →

Error Reference

Every error modelBridge can show — organized by category with exact steps to fix each one. Use this when you see a specific error message. Browse all errors →

How Errors Work

How modelBridge translates API errors into plain language, learns from failures, and keeps error messages up to date automatically. Learn more →


Extension not listed in Window > Extensions

Section titled “Extension not listed in Window > Extensions”
  1. Check the extension folder exists:
    ~/Library/Application Support/Adobe/CEP/extensions/com.fittoframe/
  2. Enable unsigned extensions:
    defaults write ~/Library/Preferences/com.adobe.CSXS.11.plist PlayerDebugMode 1
  3. Restart Premiere Pro completely — quit and relaunch, not just close and reopen
  • The local Node.js server may not have started. Wait a few seconds — the plugin auto-starts the server on panel open
  • Check if Node.js is installed: open Terminal and run node --version. If not found, install Node.js from nodejs.org
  • If the panel stays blank for more than 10 seconds, close and reopen it from Window > Extensions
  • For persistent issues, see Server & Connectivity

The local backend server lost connection. Click the Reload button in the error message. This triggers a full recovery sequence: health check → restart if needed → wait for healthy → retry.


Some models experience queue times during peak usage on fal.ai. This is normal for popular models — especially high-quality video models.

  • Wait — queue times vary from seconds to a few minutes
  • Switch models — try a faster model (e.g., LTX 2.3 instead of Kling v3 Pro)
  • Check fal.ai status — if all models are slow, fal.ai may be experiencing high load

If a generation stays queued for an extended period, it automatically moves to background processing.

Heavy models (Kling v3 Pro with audio, Veo 3) can take 5–15 minutes. The progress button updates its message over time:

  • “Generating…” → “Sit back and relax…” → “Still working on it…” → “This model takes a while…”

If the generation exceeds the expected time, it moves to the background automatically. Check the Active Generations Panel for status.

Your fal.ai account has run out of funds. Add credits at fal.ai/dashboard/billing. After topping up, the next Generate click shows a confirmation: “Have you topped up?” — click yes to proceed.

The button stays disabled until all requirements are met. Hover over it for a tooltip explaining what is missing:

  • “Add a prompt to generate” — the prompt field is empty
  • “Select media from your timeline” — the model requires an image or video input
  • “Add your API key” — no fal.ai API key configured
  • Validation error on the media card — the selected media does not meet the model’s requirements

”Image too small” / “Image too large”

Section titled “”Image too small” / “Image too large””

The selected image does not meet the model’s dimension requirements. The error message shows the exact constraint: “Image too small (640x480, min 1024x768).”

Use a larger or smaller image, or try a different model with less restrictive requirements. modelBridge remembers these constraints — you won’t hit the same error twice.

The selected file exceeds the model’s file size limit. Try:

  • Reducing the image resolution before selecting it
  • Using a more compressed format
  • Selecting a different file

Premiere Pro sometimes returns 0x0 for certain image formats. modelBridge reads dimensions directly from the file as a fallback. If the card still shows 0x0, try re-importing the image into Premiere Pro.

The model requires an input image or video. Select a clip on the timeline, select an item in the Project Bin, or drag a file from Finder.


If none of the solutions above resolve your issue:

  1. Search the docs — use the search bar at the top (⌘K) to find specific error messages or topics
  2. Check the Error Reference — every error modelBridge can show is documented with exact steps
  3. Contact support — email support@modelbridge.app with a description of the issue and any error messages you see