---
title: "Troubleshooting"
description: "Fix common issues with canvas editing, imports, generation, preview, export, assets, and MCP connections."
locale: "en"
section: "FAQ"
updated: "2026-06-22"
source: "https://flare.design/docs/troubleshooting"
---

# Troubleshooting

Fix common issues with canvas editing, imports, generation, preview, export, assets, and MCP connections.

> Section: FAQ

[HTML](https://flare.design/docs/troubleshooting) | [Markdown](https://flare.design/docs/troubleshooting/index.md)

Use this checklist when a workflow behaves differently than expected.

## Quick diagnosis

| Symptom                           | First check                                       | Related guide                                                             |
| --------------------------------- | ------------------------------------------------- | ------------------------------------------------------------------------- |
| Import looks broken               | Simplify the source and confirm images are loaded | [Paste HTML into the canvas](/docs/paste-html-into-canvas)                |
| Layer cannot be selected          | Use the layer panel or hide overlapping layers    | [Canvas basics](/docs/canvas-basics)                                      |
| Preview is not the expected scene | Select the target frame before previewing         | [Timeline and motion](/docs/timeline-and-motion)                          |
| Export fails                      | Try a shorter or lower-resolution proof           | [Preview and export MP4](/docs/preview-and-export-mp4)                    |
| Generation is inconsistent        | Reduce variables and compare one change at a time | [Choose generation models](/docs/choose-generation-models)                |
| MCP client cannot connect         | Check endpoint, scopes, and OAuth connection      | [Configure the flare.design MCP server](/docs/configure-flare-design-mcp) |

## Import does not look right

For HTML or Figma paste, simplify the source first. Copy real text and loaded images, avoid deeply nested wrappers, and rebuild complex unsupported effects directly in the canvas when needed.

For HTML, paste structure that already renders correctly in the browser. For Figma, copy the frame or layers you actually need instead of a large surrounding workspace.

## A layer is hard to select

Use the layer panel, zoom in, or temporarily hide nearby layers. If content is inside a frame, selecting the frame first can make nested content easier to reason about.

If selecting a group changes too much, expand the group and select the child layer directly. Rename important layers once you find them.

## Motion preview differs from the layout

Select the target frame and preview from that frame. Check layer start and end times, hidden states, video trim handles, and any motion clips that may be active.

If a layer appears too early or too late, fix its layer range before adjusting keyframes. Ranges are easier to reason about than custom motion clips.

## MP4 export fails

Try a shorter frame first. Browser-side export requires WebCodecs support, so test in a current Chromium-based browser if local export is unavailable.

For cloud renders, check the quote before starting and confirm the workspace has the required plan allowance or Flares balance.

## Generation results are inconsistent

Reduce the prompt to the main subject, style, aspect ratio, and intended use. Compare one model or parameter change at a time.

Keep a small comparison frame for model tests. Place outputs at the final size and judge them with real copy, not only as standalone images.

## MCP authorization fails

Reconnect the client, confirm the resource URL is `https://mcp.flare.design/mcp`, and request only the scopes required for the task.

If a tool is missing after authorization, check whether the requested OAuth scopes include the matching read or write capability. Ask for the smallest scope set that supports the workflow, then reconnect.

## When to contact support

Capture the project name, workspace, browser, approximate time, and the action that failed. For MCP issues, include the client name, requested scopes, and whether OAuth completed before the tool call failed. Avoid sending secrets or bearer tokens in support messages.