Why Your DJI Pocket 3 LUT Looks Too Strong
Troubleshoot harsh contrast, oversaturated color and odd skin tones after a Pocket 3 LUT. Check the input profile, duplicate transforms, balance and strength.
Quick answer
Check the clip's profile and the LUT's intended input first. Then isolate duplicate looks or conversions, balance exposure and white balance, and adjust creative strength. If the image changes only after export, check output settings before altering the grade.
A LUT can make a Pocket 3 clip look too dark, too orange or much more saturated than expected. Lowering its strength may help, but first establish whether the file is being used in the workflow it was designed for.
Work on a duplicate of one short clip. Change one thing at a time and compare at the same frame. This guide is for a LUT that imports but produces an unexpected image. If the file will not import at all, start with the file and app checks in our usage guide.
Start with the symptom
The same appearance can have several causes. Use this table to choose the first check, rather than treating it as a diagnosis from the image alone.
| What you see | First check | What to try next |
|---|---|---|
| Heavy contrast and blocked shadows | Wrong input or a repeated conversion | Verify the profile and inspect the processing chain |
| Strong orange skin or bright green foliage | Source balance, another look, or creative strength | Compare without the creative LUT, then rebalance |
| A flat or washed-out image | Missing or mismatched log conversion | Follow the LUT maker’s intended input and output |
| One shot looks fine; the next looks wrong | Lighting and exposure differences | Balance the clips individually |
| Editor preview looks fine; export does not | Output settings and playback conditions | Compare a short export before changing the look |
1. Match the LUT to the recorded profile
“For Pocket 3” is not enough information. A LUT may expect Normal, untreated D-Log M, or an image that has already passed through a particular conversion. Read the file’s instructions, not just the product name or .cube extension.
DJI documents Normal, HLG and D-Log M as separate options. Its official Pocket 3 D-Log M to Rec.709 LUT is a conversion for D-Log M input; it is not a general enhancement for Normal footage.
Verify the original clip’s profile from the recording workflow or shooting notes. A preview that looks flat is a clue, not proof: apps can apply viewing transforms. The camera’s current profile also does not identify an older file.
If you recorded Normal, use a look explicitly made for that input. If you recorded D-Log M, follow the matching conversion or combined conversion-and-look instructions. HLG needs its own workflow. Our Normal vs D-Log M guide explains the distinction.
Reducing a mismatched LUT to 20% can make an image less extreme without making the underlying workflow correct. Fix the input mismatch before judging the style.
2. Check for a look or conversion applied twice
There may be more processing than the visible LUT control suggests. Inspect clip effects, adjustment layers, nodes, project color management and any filters applied before the file reached this project.
For example, a D-Log M creative product might already include the conversion it needs. Adding a separate conversion in front of it could give it the wrong input. Another product might require a prior conversion. Follow the instructions for the actual file; neither arrangement is universal.
On your duplicate clip, bypass optional creative effects one at a time. Leave the necessary viewing or output transform in place while assessing a log workflow. Turning everything off can make log footage look flat by design, which does not identify a fault.
If the source is an exported social video with an existing look, use the original camera file when possible. A second LUT cannot reliably undo the first grade. A lower overall saturation value will not reconstruct the original colors either.
3. Compare exposure and white balance without the creative look
For a Normal clip, bypass the creative LUT and inspect the baseline. For log footage, keep a correct viewing conversion so that the comparison is meaningful. If skin already looks orange or a face is too dark at that stage, correct that before asking the creative LUT to carry the image.
Use exposure to establish the subject’s brightness and temperature/tint to address an unwanted color cast. Adobe’s basic correction reference describes those controls; exact slider values and processing order depend on your editor.
A useful practice scenario is a person beside a cafe window with a warm lamp behind them. If the face and background are lit differently, a single white-balance change may improve one and worsen the other. Decide which area matters most, rather than forcing the whole frame to neutral.
Avoid repeatedly adding saturation, contrast and shadow recovery to cancel one another. Return to a simpler baseline, then re-enable the look. When the editor exposes processing order, use the correction placement recommended for that LUT; the order in which you click controls is not necessarily the order of processing.
4. Adjust creative strength after the workflow is correct
Once the input and balance are right, the look may simply be stronger than you want for that scene. Reduce the creative LUT intensity if the editor provides that control. Review faces and strong colors as well as the overall mood.
There is no required percentage for a “professional” result. Different LUTs, editors and scenes respond differently. Compare several strengths on a short clip and choose the amount that serves the shot.
Do not automatically use the same approach on a technical conversion LUT. Blending an essential conversion halfway with unconverted log footage can leave a partially transformed image. Keep conversion decisions separate from the strength of a creative look, following the maker’s workflow.
If the app has no suitable intensity control, do not assume reducing saturation is an equivalent substitute. A LUT may also change contrast and the relationships between colors. Use a supported method in your editor or choose a more suitable look.
5. Distinguish lost detail from a dark grade
Compare the affected area with the source under the correct viewing conditions. If a dark jacket has texture before the look but becomes a solid patch afterward, adjust the look or its tonal balance. If there was no usable texture in the recorded image, a LUT cannot invent an accurate recovery.
The same check applies to bright skies and pale walls. A LUT can change how recorded detail appears, but it cannot restore highlight information that was clipped at capture. This is a reason to judge exposure on location, not a reason to keep stacking corrective effects later.
For a complete Normal editing sequence, use the Pocket 3 Normal color-grading workflow.
6. If only the export looks wrong, check delivery
Keep the grade as it is while testing this branch. Export a few seconds and compare the saved file with the preview on the same display under similar viewing conditions. Check the intended SDR or HDR output, the export preset and the player’s treatment of the file.
Then compare the local file with any uploaded version. If the difference appears only after upload or only in one player, that narrows the investigation; it does not by itself prove the LUT is broken. Avoid compensating for one display by applying an extreme grade that looks wrong elsewhere.
Using Negative 01 or asking for help
The included Negative 01 file expects Normal footage. It is a creative look, not a D-Log M conversion. For footage already shot in D-Log M, ask about the buyer adaptation; do not assume a converted D-Log M clip is identical to the camera’s Normal rendering.
If you contact the LUT maker, include the camera and recording profile, LUT filename, editor and version, whether the source is original or already exported, and where the problem appears. A description such as “the preview is fine but the saved file is darker” is much more useful than “the LUT does not work.”
For DLOGM support, use the usage help form. Share only material you have permission to share, and keep private order-download links out of screenshots and public posts.
References and scope
Checked October 28, 2026. This is a troubleshooting method, not a claim that a particular defect has been reproduced in every app. Scene examples and the cover illustration are explanatory, not product-test results.