DJI LRF Files: Identify a Proxy and Check Its Original

Distinguish DJI LRF proxies from original recordings, inspect copied files, and verify whether a lower-definition version covers the intended clip.
XAppSet Team
Published on November 14, 2026

A DJI .LRF file can preserve a lower-definition version of a recording, but it is not the full-quality original. Keep it alongside any original video and related files, then check what it actually contains. Renaming a working copy may make a supported LRF file playable; it cannot recreate resolution or recording data absent from that copy.

SD and microSD cards beside a USB reader and camera

Establish which DJI product made the file

Start with the camera model, recording mode, and location from which the file was copied. A file copied from a memory card, an app cache, and an exported edit may represent different versions of the same scene.

DJI’s LRF support article identifies compressed LRF files used for playback, preview, and Trim Download on listed Osmo Action and Pocket products, including Osmo Action 4 and Osmo Pocket 3. It also describes using a remaining LRF when the related MP4 is missing. That documented behavior should not be expanded into a single file-layout rule for every DJI aircraft and camera.

Check the instructions for your exact model through the DJI Download Center. Do not assume that every device creates the same companions, stores an extra internal copy, or uses the same naming convention.

Distinguish a proxy, a thumbnail, and an original

A proxy is an alternative video representation used to make viewing or editing more convenient. A thumbnail represents an image of a moment. The original recording is the source you need when the task requires the camera’s recorded quality and full retained content.

An LRF containing a playable sequence is therefore different from a still thumbnail. A thumbnail in a file browser may show just one small image. It does not tell you whether the proxy or original video plays from beginning to end.

Keep all available companions during the initial review. A smaller file can still be useful for recognizing the scene or checking continuity, but size alone cannot establish its role. An original recorded at a lower setting can also be small.

Inspect copies before changing names

Create a working folder on a healthy destination and retain the copied files with their original names. Record each file’s source path and byte size. Keep the original card unchanged if you are dealing with deleted or missing footage; this identification task does not require recording a new clip or formatting the card.

On a working copy from a model covered by DJI’s guidance, changing .LRF to .MP4 can allow the lower-definition video to open. Preserve the .LRF copy separately and record the new name. Changing the suffix changes the label, not the encoded picture quality.

If the renamed copy still does not open, do not infer that more renaming or transcoding will repair it. The file could be incomplete, unsupported by that application, or different from the documented case. Retain it and inspect its structure before choosing another action.

Record the video properties

Use the media-information view in a suitable application to record dimensions, duration, codec, frame rate, and audio-stream presence. Where a command-line inspection is appropriate, ffprobe can report container and stream information. For an already copied file, this example requests those properties without creating a converted video:

ffprobe -v error -show_entries format=format_name,duration:stream=index,codec_type,codec_name,width,height,avg_frame_rate,duration -of json "clip-copy.mp4"

Replace the example filename with the working copy’s path. If a value is missing or the command returns an error, record that outcome rather than filling in an expected resolution or duration.

Do not classify every file with one particular dimension as an LRF proxy. Model settings, exports, and other sources can overlap. Interpret the properties together with the source and actual recording content.

Match a proxy to the right recording

If both versions are available, compare their visible content and timeline. A similar base name is a useful lead, but a recovery tool may have generated names and timestamps may reflect copying or incomplete metadata.

Look for recognizable events near the start, middle, and end. Check whether the same scene occurs in the same order, whether either version ends early, and whether there are gaps. Record sound only when an audio stream actually exists; its absence is not automatically evidence of loss for every recording setup.

Use a simple pairing record:

Field What to record
Source Camera model and original location, when known
Candidate pair Both unchanged filenames and working-copy names
Properties Dimensions, duration, codec, and audio presence for each
Correspondence Matching visible events and any unexplained differences
Conclusion Confirmed correspondence, plausible match, or unresolved

Play each accessible file through before deciding that it covers the entire event. Matching start frames do not establish matching endings, and matching duration alone does not establish identical content.

When only the lower-definition copy remains

Preserve the LRF and any playable derivative as separate files. Label the usable result clearly as a lower-definition copy. It may be sufficient for a personal record, a rough edit, or identifying which original recording is missing; whether it meets a delivery requirement depends on that requirement.

Upscaling changes output dimensions but does not retrieve the original recorded pixels. Similarly, converting a playable proxy to another codec creates a derivative of the proxy. Keep those versions apart from recovered originals so that a convenient MP4 filename does not conceal the quality difference.

If full quality is still required, search existing backups, prior card copies, and verified original downloads before treating the proxy as the final answer. For genuinely missing original files, follow the camera video recovery guide with the original medium preserved. Do not erase the card merely because a preview survives.

The decision is then concrete: an original has been located and checked, a lower-definition copy is usable for a stated purpose, or the relationship remains unresolved. Each is a more accurate result than calling every playable companion a recovered original.

Camera photo and video recovery guide

Privacy Overview
XAppSet

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful. Privacy Policy

Strictly Necessary Cookies

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.