> ## Content Index
> Fetch the complete content index at: https://lightworksguide.net/llms.txt
> Use this file to discover other available public pages before exploring further.

# Lightworks Export Looks Blurry: Find Where Detail Was Lost
- URL: https://lightworksguide.net/fix/blurry-export/
- Published: 2026-10-22T09:00:00.000Z
- Updated: 2026-11-17T23:15:44.000Z
- Author: Lucas Bennett
- Tags: fix

If a Lightworks export looks blurry, check the completed file's pixel dimensions and view it at actual size before changing compression. Then compare the same content in the original, the sequence, the local export and the uploaded version to find where detail first changes. I'd keep one short, clearly named local export as the baseline: changing several settings or judging only the upload makes the cause harder to isolate.

A small picture enlarged across a screen, a punch-in on low-resolution footage and compression breakup in motion need different fixes. Start with the symptom that matches your file.

| What you see                                                          | Check first                                                            | Next action                                                                |
| --------------------------------------------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| The local file is smaller than intended                               | Actual output dimensions, exported item and target                     | Compare the file with the chosen size in Export; don't trust its filename. |
| Originals are clear, but a cropped shot looks soft                    | Scale, crop, Reframe and effect stack                                  | Bypass one treatment in a sequence copy and compare the same moment.       |
| A still looks good, but moving detail breaks up                       | The same motion range at fixed size/rate and known viewing scale       | Compare only export controls your edition offers; record the encoder too.  |
| The file looks right in one player                                    | Player magnification and playback behaviour                            | Investigate that player difference before re-encoding.                     |
| Local output is clear; only YouTube is soft                           | Processing and the selected playback rendition                         | Check Settings → Quality on the watch page; retain the good local file.    |
| The picture is stretched, cropped differently or an overlay has moved | Source/output shape, framing and effects at the intended delivery size | Treat it as a geometry difference before calling it compression blur.      |

## Start with a finished file and online originals

Confirm that the export finished and open the file at its actual destination. An older MP4 with a similar name is an easy false comparison. The current [Tasks page in project settings shows background jobs, while Tasks Log records completed work](https://lwks.com/lightworks-knowledge-base/batch-export-and-background-tasks). An aborted export discards that render. For a failed job, a tiny incomplete file or a file that stops early, use the [export failure checklist](https://lightworksguide.net/fix/export-failed/) first.

Check the originals used throughout the affected sequence, including background layers. Lightworks normally exports from original media, but its [proxy guide warns that export falls back to available media when originals are offline](https://lwks.com/lightworks-knowledge-base/proxies-and-performance-media). A proxy playing successfully or a clip retaining its metadata doesn't establish that its original is available.

Reconnect the source drive, or restore a moved file to its original path and refresh. The [media management guide also supports relinking a clip to its correct original in a new location](https://lwks.com/lightworks-knowledge-base/media-management). Confirm the replacement's identity and full-resolution media before using it. Don't delete proxies to force a quality change; reconnecting the originals addresses the dependency without removing useful editing media.

Once the required originals are online, choose one affected shot with fine detail and a short section containing motion. Note a recognisable frame and its sequence timecode. Keep this range and your intended framing fixed while diagnosing the output.

## Record the source, intended export and actual file

Write down the original's dimensions, the size chosen in Export and the completed file's dimensions. Record frame rate and codec alongside them. Also note the sequence's intended shape and any crop or punch-in: a 1920 × 1080 file can contain an enlarged portion of a much smaller picture.

### Read the intended source

Open the original clip in the source viewer and make it active. In **Info → Metadata**, confirm the **Source:** name identifies that clip, then read its **Frame rate**, **Video format** and **Compression**, plus aspect ratio where relevant. The [Info panel follows the active item and exposes read-only technical properties](https://lwks.com/lightworks-knowledge-base/clip-information-and-metadata). Recheck its name after changing selection; a Sequence: line means you're reading a different item.

### Make one short local baseline

I'd use the full Export panel for this check because [an Auto start preset can begin immediately](https://lwks.com/lightworks-knowledge-base/export-overview), before you've inspected its choices.

1. Open the intended sequence. Mark the affected range, using **I** and **O** with the sequence active, rather than marking a source clip.
2. In the timeline toolbar, open the **Tools** side menu and choose **Export**. Expand **Source**, confirm the intended sequence and remove unintended items from this diagnostic list. Under **Region → Selection**, choose **Marked section**; scroll below Audio if Region isn't visible.
3. Choose the required preset, or **Custom** to inspect settings manually. Check **Video**, including **Size/rate**, format and codec. Use the intended delivery size and sequence frame rate.
4. Under **Destination**, choose a local folder and a distinct name, such as **DetailCheck\_baseline**. Keep any cloud upload option off for this comparison.
5. Start the export, wait for completion, then open that destination file outside Lightworks. Keep its settings and the file for comparison with the next export.

The [current timeline Tools menu includes Export](https://lwks.com/lightworks-knowledge-base/timeline-tools-and-commands), and the [Export workflow supports a whole item or marked region, with licence-dependent output choices](https://lwks.com/lightworks-knowledge-base/export-overview). For selecting a different item or preparing the full delivery, use the [export settings guide](https://lightworksguide.net/export/settings/). This diagnostic range is for finding the difference; it doesn't replace watching the final full-length file.

### Inspect what was written

On a Mac, open the file in QuickTime Player and choose **Window → Show Movie Inspector**, or press **Command-I**. Apple's [Movie Inspector instructions cover the file's size, frame rate and compression information](https://support.apple.com/guide/quicktime-player/view-information-about-a-movie-file-qtp65619118c/mac). This avoids changing Lightworks' import defaults.

A documented route inside Lightworks is to right-click in a bin, choose **Import**, browse the drive containing the completed output and select that exact file. Use **Create Link To Media** and **Add to bin → New Bin**; give the bin a diagnostic name. The [Import panel can link directly to media and remembers the chosen method for subsequent imports, including drag and drop](https://lwks.com/lightworks-knowledge-base/importing-media). Restore your usual import method afterwards.

Open that linked output in the source viewer, confirm its Source: name in Info and inspect Metadata. Keep it out of the edit and leave the linked file in place. If this format requires conversion or a direct link is unavailable, stop this inspection route: a converted clip would no longer be the unchanged output you're trying to measure.

[![Info Metadata panel for DetailCheck_baseline.mp4 showing 25 fps, 1920x1080 Video format and H.264 Compression](https://lightworksguide.net/content/images/2026/11/lightworks-blur-output-metadata-20261118.webp)](https://lightworksguide.net/content/images/2026/11/lightworks-blur-output-metadata-20261118.webp)

Read the completed output as its own source item. Compare these properties with the original and the size chosen in Export.

**Example:** a 1920 × 1080 original, a chosen 1280 × 720 export and an actual 1280 × 720 file show that the selected downscale happened. Enlarging that file cannot restore the original's detail. If you chose 1920 × 1080 but obtained 1280 × 720, recheck the exact completed item, target, preset and licence before changing bitrate.

Exporting a small, already compressed edit and importing that MP4 for another round of editing adds another compression generation. In a [2020 Lightworks quality discussion about repeated 720p exports](https://forum.lwks.com/threads/export-quality.224462/), the useful remedy was to return to the original material and edit rather than keep recycling the smaller output. A larger output setting or a paid licence doesn't reconstruct detail discarded earlier. Go back to the original sequence and media when they're available.

## Compare detail and motion at a known scale

Park on the same content in the original, sequence and exported file. Use a recognisable feature to match the frame as well as your timecode; the exported range can start at a different time origin. In Lightworks, [100% displays one screen pixel per video pixel, while Fit scales the picture to the viewer](https://lwks.com/lightworks-knowledge-base/viewers-and-playback). Source and sequence viewers zoom independently. Equal-sized windows don't mean equal magnification.

Choose **100% (Actual Size)** from the viewer's zoom control for fine-detail inspection. With originals online, select **Quality → Highest available** for the source comparison; [Lowest available uses proxies where they exist](https://lwks.com/lightworks-knowledge-base/proxies-and-performance-media). This changes playback media, not the export's bitrate. If only the preview improves and the local output was already clear, you haven't found an export defect.

[![Lightworks source viewer zoom menu with 100% Actual Size selected over a detailed mug and wood surface](https://lightworksguide.net/content/images/2026/11/lightworks-blur-viewer-actual-size-20261118.webp)](https://lightworksguide.net/content/images/2026/11/lightworks-blur-viewer-actual-size-20261118.webp)

Set each viewer's scale deliberately. Fit can hide a detail difference or enlarge a smaller image.

In QuickTime Player, **View → Actual Size** displays the movie at its source size; [Window → Fit to Screen scales it to the screen](https://support.apple.com/guide/quicktime-player/choose-a-screen-size-qtp31dfa136d/mac). Outputs with different dimensions can occupy different amounts of screen space at actual size. Filling the same window would enlarge the smaller one more.

Now play the short motion range. Look for a change in fine moving texture or picture breakup, rather than judging one paused frame. The [web delivery guide recommends checking a motion-heavy section because too little bitrate can break up the picture](https://lwks.com/lightworks-knowledge-base/web-and-social-delivery). A good still and poor motion narrow the investigation, but don't establish bitrate as the sole cause.

If the original itself is soft, consider focus, recorded motion blur or previous source processing before touching export controls. If the original is clear but the sequence is softer, inspect its treatment next. If both are clear and only the finished file differs, continue to the player and export comparison.

## Separate framing and effects from lost detail

[Crop hides edges, Scale enlarges or reduces the picture, and Reframe adapts its delivery shape](https://lwks.com/lightworks-knowledge-base/transform-crop-and-reframing-tools). Enlarging a small part of a source spreads its remaining detail across more of the output frame. Those treatments affect the saved picture. Viewer guides are display aids; they don't apply a crop or change the media.

Preserve a sequence copy before adjusting treatment. Select the affected segment, or target the relevant track for a track effect. Note crop, scale, position, animated values at the affected moment and stack order. Bypass one suspected effect, then compare the same frame and motion range at the same viewing scale. The [effects workflow retains a disabled effect's settings, and processing order changes the result](https://lwks.com/lightworks-knowledge-base/effects-overview).

If bypassing improves the picture, decide whether the intended framing is worth that detail tradeoff and adjust that treatment deliberately. If it makes no relevant difference, restore it. I'd leave sharpening out of this diagnosis: changing edges at the same time makes the first loss harder to locate.

A stretched frame, displaced title or unexpected black border is a different symptom from compression blur. Compare the source and delivery aspect ratios and review the affected effects at the intended output shape and size. A [2019 split-screen discussion reported a preview/export mismatch involving cropped effects and differing output geometry](https://forum.lwks.com/threads/exported-video-looks-different-from-the-preview-in-media-viewer.202010/). Its old Project Card instructions aren't the current Export route; the useful check is to hold geometry steady for the diagnostic export, then review a separate social reframe as its own delivery.

For the full framing operation, use the [crop and resize guide](https://lightworksguide.net/editing/crop-resize/). Changing the player window after export only changes display size; it doesn't rewrite the file's pixel dimensions.

## Change only export controls your edition offers

First play the same completed file in another player already available to you, at a known scale. If only one player shows the problem, keep the file and investigate that playback difference before re-encoding the sequence.

The [current plan matrix lists maximum export resolutions of 1080p for Free, 4K for Create and 8K for Pro](https://lwks.com/pricing). The current [web delivery guide includes portrait and 1080p output on Free](https://lwks.com/lightworks-knowledge-base/web-and-social-delivery). Older 720p-only advice doesn't describe the current release. These are ceilings, not a promise that every source or preset uses the maximum. The [resolution limits guide](https://lightworksguide.net/export/resolution-limits/) covers plan and actual-file checks.

If the panel offers fewer choices than expected, [open the avatar at the top right of the Project Browser to check the licence type; Activate licenses opens licence management](https://lwks.com/lightworks-knowledge-base/application-preferences). Confirm the installed build too, especially when following an older tutorial.

**Free and Create:** the plan matrix reserves [manual H.264 bitrate configuration for Pro](https://lwks.com/pricing). Use the actual target, preset and size choices offered. Compare an alternative preset only if one is available. Because a preset can change several settings, an improvement identifies a useful export choice without proving which individual parameter caused it. The viewer's proxy Quality menu isn't a substitute bitrate slider.

**Pro, when the chosen target exposes manual H.264 controls:** record the baseline bitrate and encoder, then compare a higher bitrate on the same motion range. Keep source media, range, effects, dimensions, frame rate, codec, encoder and the other settings fixed. Use a new destination name, wait for completion and verify the resulting file's dimensions and frame rate before judging it.

[![Lightworks Pro H.264 Export panel with DetailCheck sequence, local baseline destination, 1080p25 Size/rate and 8 mbits variable bitrate](https://lightworksguide.net/content/images/2026/11/lightworks-blur-export-panel-20261118.webp)](https://lightworksguide.net/content/images/2026/11/lightworks-blur-export-panel-20261118.webp)

Pro H.264 example on macOS: record Size/rate, bitrate and encoder before changing one setting. The shown 8 Mbps is an example, not a universal quality fix.

For a numerical reference, [YouTube's SDR upload recommendations give 1080p video 8 Mbps at 24/25/30 fps and 12 Mbps at 48/50/60 fps](https://support.google.com/youtube/answer/1722171?hl=en). These are upload recommendations, not minimum-quality guarantees for every source or every Lightworks encoder. Mbps means megabits per second; the panel's **Bit rate (mbits)** is not megabytes per second. Grain, fine moving detail and prior compression can make a particular sample demanding even at an otherwise sensible delivery setting.

Keep the finished sequence's rate for this comparison, as the [Lightworks delivery guidance recommends](https://lwks.com/lightworks-knowledge-base/web-and-social-delivery). Doubling the export frame rate to chase a bitrate recommendation adds another variable. HDR has separate delivery requirements; don't apply that SDR reference table as an HDR prescription.

The encoder matters too. In an [October–November 2026 Windows 11/Nvidia encoder comparison](https://forum.lwks.com/threads/bframes-and-export-quality.254015/), different H.264 encoders produced different stream structures at the same nominal settings. The author later revised an alarming quality conclusion after changing the source from raw video to H.264 MP4\. My takeaway is to compare your actual source and keep the encoder name in the record, rather than assume that a preset called Master guarantees a particular result or that one test condemns every export.

If a bitrate comparison helps, verify the final full export with that setting. If it doesn't, restore the baseline rather than keep increasing numbers. Where another encoder is offered, compare it separately while retaining the other settings; name that output separately too. A remaining source/codec-specific difference needs the source format, build, platform and encoder in the support report. No export setting can recover detail absent from the available original.

## When only the uploaded version looks soft

If the local output is acceptable, keep it as the reference. YouTube [processes low quality first and makes higher qualities available after their processing finishes](https://support.google.com/youtube/answer/71674?hl=en). Open the watch page and choose **Settings → Quality**; select the intended rendition when available, then compare the same content. A lower available playback rendition doesn't establish that Lightworks encoded that lower resolution.

There isn't one waiting time for every upload, and processing won't restore source detail missing from the uploaded file. If the intended rendition is available but still looks poor, record its selected quality, player and device. Keep the issue in the platform branch instead of altering a local master that already looks right. For preparing the upload itself, follow the [Lightworks to YouTube workflow](https://lightworksguide.net/export/youtube/).

## Send a report that identifies the first difference

The [Lightworks support guidance asks what you did, what happened, the media format, version and system information](https://lwks.com/lightworks-knowledge-base/troubleshooting-common-problems). For soft output, include:

- Exact build, operating system, licence and encoder; original dimensions/frame rate/codec, chosen export settings and actual completed-file properties.
- Sequence or clip name, exported range and destination filename; whether every required original was online.
- An affected timecode and recognisable frame, intended output shape, crop/scale/effect state and viewer/player magnification.
- The first stage that changes: original, sequence, local file or upload. Describe the still and motion results separately.
- The baseline and comparison settings, what improved, what made no difference and whether another player displays the same file differently.

Keep a short shareable example with those settings if you can provide one without exposing private footage. That gives support a specific source-to-output problem to investigate, rather than an unbounded request for the best export settings.