Folio for FigmaComing soon to the App StoreComing soon

Troubleshooting

White page or stalled file

Check your connection, then use Reload from the browser controls/menu. If a document tab was unloaded to save memory, selecting it starts loading again. A brief loading indicator is expected.

After repeated WebContent termination, Folio offers Reload or Safe mode. Safe keeps the native browser controls but disables compatibility scripts and input adaptations. If Safe loads successfully, record which input settings were enabled before the failure. Change back to Normal in Developer Tools > Modes when ready; changing mode reloads the current tab.

Memory and unloaded tabs

On iPad, Automatic memory policy keeps tabs until iPadOS memory pressure; a 3/5/8 cap unloads background documents sooner. On iPhone, Automatic keeps one live file plus Home; the explicit cap is two files. Home, visible tabs and pending authentication/export/download work stay protected. Unloading does not close the tab, but returning reloads its file and may lose transient editor state.

Try fewer open files or a lower cap in Settings > General if failures repeat. WebKit’s termination callback does not identify the cause, and Folio’s available-memory number measures the host app allowance, not Figma’s WebContent usage. A termination alone is not proof of a memory limit.

Keyboard focus or unexpected input

Tap the intended Figma field or canvas before typing. Close Folio overlays with Escape. Try Option+Command+Left/Right for tab changes while typing; Control+Tab yields to a visible editor. Release locked bottom-toolbar modifiers if dragging or keys act unexpectedly.

If the keyboard stops reaching Figma, try backgrounding and reopening Folio, then restarting the device if needed. Compare the same action in a fresh tab. Record whether a hardware or on-screen keyboard was in use. Do not enable experimental focus switches as a routine fix; their benefit for real Figma text is not established.

A docked on-screen keyboard bounds the browser above it and covers the bottom toolbar. Floating and undocked keyboards keep WebKit’s own field-reveal behavior. If a field remains hidden, dock or move the keyboard and report the field type, keyboard layout and interface zoom. Folio tab/window shortcuts yield while IME text is being composed; commit or cancel the composition before using them. The hardware-keyboard shortcut bar keeps WebKit’s default behavior.

iPhone panels (Alpha)

If the canvas above an open sheet is offset or a Figma menu opens off-screen, turn off Developer Tools > Input > Canvas beside panels (experimental). If the canvas does not fill the screen, Layers or Properties fails to open a sheet, or a panel is misplaced, turn off Developer Tools > Input > Phone panel layout and use Figma’s own Minimize UI or Expand UI control. Hiding the bottom toolbar also shows Figma’s tool bar and rail again. Record the route type, orientation and interface zoom. See the iPhone Alpha guide for confirmed behavior and remaining device checks. Requesting the desktop website does not bypass Figma’s restrictions.

Sign-in and fonts

Google login is blocked in the embedded browser. Use an eligible Figma email/password or organization SSO method, or use Safari. A Safari session cannot be transferred to Folio. See getting started.

The font library imports static original TTF/OTF/TTC files you are licensed to use. Import success does not mean Figma can discover the fonts. The local Figma connection is Debug-only and OFF by default; if it cannot connect safely, leave it off. Do not bypass certificate or transport checks.

Share a Developer Tools report

  1. Open ⋯ > Developer Tools or press Option+Command+I. Note the Folio version/build, device model and iPadOS or iOS version.
  2. Describe the action that failed and whether it repeats in another tab or Safe mode. If input evidence is needed, enable the relevant optional logging, reproduce briefly, then turn logging off.
  3. Use Overview’s report controls to copy or Share report. Share only when you choose; Folio does not upload reports automatically.

Reports use sanitized metadata and omit file keys, titles, auth URLs, document text and typed input. Do not add passwords, authentication links, private design text or account screenshots to your description. Testing labs exercise local fixtures; they do not prove real Figma input or authentication works.