View all guides

Troubleshooting

What to check when a document conversion or recording fails

First find whether the structure was lost during copy, Chrome prevented the selected tab from recording its audio, or the device ran short of storage. Once you know the stage, use the matching import or export route.

ResultA clear distinction between source, browser, format, and storage problems
01

Paste lost every heading and table

The source probably supplied plain text instead of structured clipboard HTML. Use Quick Send on a selected region or open an HTML export rather than repeating the same paste.

  • Check whether Command/Ctrl+Shift+V forced plain text
  • Rewrite merged-cell layouts as simple tables or lists
  • Canvas, iframe, and video do not map to Markdown
02

Links and images fail for another reader

Relative URLs, authenticated attachments, and intranet paths can be valid Markdown but still fail outside the original session. Check absolute URLs and permissions separately.

03

TAB.REC starts but captures no useful audio

  • Confirm audio is playing in the selected Chrome tab
  • Check whether protected media or browser policy blocks tab capture
  • Make sure playback did not stop or reload during recording
  • Microphone and full-system audio are not TAB.REC sources
04

A long recording or conversion stops

Check device sleep, browser closure, and free storage first. Studio uses the current device's CPU and memory, so large files need time. Split by duration or expected size when the output is large.

  • Export important recordings after completion
  • Keep the tab awake during conversion
  • Preserve the source WebM before retrying
05

What to include in a support report

You do not need to send the document or audio. Browser and operating system, file type and approximate size, the sequence of actions, and the visible error message are enough to start narrowing the cause.