When a video will not show up on an editing screen, the next useful step is identifying where the picture disappears. A blank timeline, a stalled import and a black preview with working audio are different symptoms. Re-uploading the entire project repeatedly can hide the distinction.
This guide provides a practical diagnosis order and an original conversion example checked October 2, 2026. The example uses a synthetic test clip, not a claimed repair of every editor or camera format. Keep your original media and project while testing a separate copy.
Use the local video checker to isolate the source
Choose the original downloaded clip in the checker above. It reads the file through this browser and shows available dimensions and duration. Use its playback controls to inspect the beginning, middle and end. The checker does not upload your video, identify its codec or repair the file.
| Checker result | What it tells you | Next test |
|---|---|---|
| A frame loads and the clip plays | This browser can display that source | Place it alone at the beginning of a new editor project |
| Metadata loads but playback fails later | Reading the header did not establish complete playback | Compare a short copy and inspect the original in another player |
| Unsupported-source error | The browser could not use the selected file | Check the editor’s supported formats and inspect the actual streams before converting |
| Zero-byte file | The selected file has no video content | Download the complete original again |
Save the check report to record the filename, size and observations while testing a separate compatible copy. A matching extension or reported file type does not establish the actual video codec. The result applies to this browser and this file, rather than proving compatibility with every editor.
These observations use the browser’s video dimensions and media error categories. An error narrows the next check; it does not conclusively diagnose a corrupt recording. Keep your original while investigating.
Find the first point where the picture disappears
| Symptom | First check | Useful isolation test |
|---|---|---|
| Media thumbnail exists but preview is empty | Timeline placement and playhead position | Put one clip at the beginning of a new project |
| Import stays at a loading percentage | Processing status and available device resources | Try a short compatible clip |
| Audio plays but the picture is black | Video stream codec and visible layers | Compare original playback with a converted copy |
| A saved project asks for missing files | Original location and sync status | Relink the intended source file |
| Every project fails to load | Browser app account or service state | Compare a fresh empty project |
Write down the exact symptom before changing settings. “The thumbnail loads but the first timeline frame is black” gives you a narrower test than “the editor is broken.” Note whether the problem started with a new file, a reopened project or a change in the browser.
Check the timeline before converting a file
Importing a clip into the media library may not place it in the edit. Put the clip on the timeline and move the playhead inside its visible duration. Check whether another layer covers the clip, whether the picture layer is hidden and whether an opacity control has been lowered.
A short empty gap before the first shot can produce a correctly black preview at time zero. Move into the shot instead of judging the file only from the opening preview. If the clip has a deliberately black opening frame, scrub farther into it and compare with playback outside the editor.
Create a temporary project with only that clip. If the picture appears there, return to the original project and inspect its layers, trims and effects. Converting a file that already displays correctly in isolation may add work without addressing the actual timeline setting.
Verify that you have a complete original file
Open the source in a local player and watch the beginning, middle and end. A cloud placeholder, incomplete download or very small accidental file may not contain the source you intended. Confirm the filename and file size against the original download or recording.
For a reopened project, locate the exact version used in the edit. A different file with the same name can have a different duration or framing. Relinking the wrong copy may restore a picture but change the edit. Keep the source directory stable until the finished export is accepted.
If the original itself will not play, return to the recording or generation source and inspect that export. An editor can sometimes read a format that a player cannot, but a failing source deserves its own check before you change the project.
Separate the container from the video codec
An MP4 filename describes the container, not every property of the streams inside it. A file can have an MP4 extension while carrying video that a particular browser or editor cannot decode. Renaming a MOV or MKV file to MP4 does not convert those streams.
MDN’s video codec guide describes browser support as a codec and environment question. Check the editor’s supported inputs as well. A delivery format that plays on your phone is not proof that the same file will import into every browser editing application.
If available, use a media-information tool to inspect the container, video codec, audio codec, dimensions and frame rate. Save those observations with the symptom. They make it possible to compare a working file and the failing one without guessing from their extensions.
Try a compatible copy when one file fails
Microsoft’s Clipchamp loading guide recommends trying a converted MP4 when imported media remains stuck. It notes that conversion can change the codecs even when the source already has an MP4 extension. That advice applies to diagnosing an import; it does not guarantee that all files will be repaired.
For a normal opaque video, an H264 picture with AAC audio in an MP4 container is a practical compatibility test when the editor supports it. Keep the original and give the converted file a new name. Do not silently use this copy as an archival master or a replacement for an HDR, alpha-channel or specialist production file.
With an existing FFmpeg installation, the following command selects the first video stream and optional first audio stream, then creates a separate copy. Check that your FFmpeg build includes the named encoders. The FFmpeg manual explains stream selection and transcoding; its codec documentation describes the encoders.
ffmpeg -i "source.mkv" -map 0:v:0 -map "0:a:0?" -c:v libx264 -crf 18 -preset medium -pix_fmt yuv420p -c:a aac -b:a 192k -movflags +faststart "preview-copy.mp4"The settings are an example, not a universal camera-conversion preset. Re-encoding can change picture quality. This command does not preserve an alpha channel or perform a deliberate HDR-to-SDR color conversion. Use the editor’s documented workflow when those properties matter.
Inspect the original worked conversion example
We created a three-second synthetic moving test pattern with a tone, stored as FFV1 video and PCM audio in a Matroska file. Running the command above produced a 640 by 360 H264 and AAC MP4 at 24 frames per second with the same three-second duration. Those are file-inspection results, not a performance or quality ranking for online editors.
Download the synthetic source and download the converted example to compare them in your own editor. A supported test clip can help separate a source-specific import problem from a project or browser problem. It cannot prove that another recording will behave identically.
When every file or project fails
If a fresh project and a known working clip both fail, inspect the application environment instead of converting more footage. Check the provider’s current service status and supported browser guidance. Note whether the issue affects one project, one account or all projects on that device.
Microsoft’s loading guide also discusses refreshing or reopening a project and making enough memory and disk space available. Preserve your originals before any cache-related recovery steps, and follow the application’s own instructions. A busy device can make processing slower, but that observation alone does not identify a damaged file.
Change one condition at a time and record the outcome. Comparing a supported browser or an empty project is useful only if the same clip and account remain the comparison inputs. Several simultaneous changes can restore the preview without telling you what actually mattered.
Verify the fix in a short export
After the picture appears, export a small representative segment. Watch for audio timing, the intended crop, orientation, color and missing frames. An editor preview can be correct while the final export uses different settings. Keep the working copy and original until the export is accepted.
For the next creator clip, start with a clear scene and retain the downloaded source. Clout lets you build original characters and generate related photos and videos. Keep the accepted clip separate from caption and delivery versions so future edits have a clean starting point.
Continue with planning original AI video scenes, readable centered captions or the Higgsfield MCP workflow guide. Each addresses a different stage after the media-import problem is isolated.
