DNG Presets Importing But Not Applying? Your Ultimate Troubleshooting Guide for 2026

DNG presets importing but not applying in Lightroom? Here’s the fix workflow that actually works

If your DNG presets are importing but not applying in Lightroom (Lightroom Classic, Lightroom Mobile, or even Adobe Camera Raw), you’re not alone. This usually shows up as the preset “loading” into your library—but your photo stays exactly the same, like nothing happened. The good news: in most cases, it’s not your photo and it’s not “broken forever.” It’s a workflow mismatch (DNG vs XMP), a profile/version conflict, or a simple caching/permissions issue.

And if you want a reliable set of presets that includes both DNG and XMP formats (so you always have a Plan B when one format acts weird), start with the 1000+ Master Lightroom Presets Bundle and browse the Lightroom Presets for Mobile & Desktop collection. If you’re building a full toolkit, you can Buy 3, Get 9 FREE when you add 12 items to your cart.

What a “DNG preset” really is (and why it can look like it applied… but did nothing)

Here’s the key misunderstanding: a lot of “DNG presets” aren’t imported the same way as normal Lightroom presets.

XMP presets are true preset files. You import them into Lightroom/ACR, and they appear in your Presets panel.
DNG presets are often DNG photo files that contain an edit “look.” You typically open/import the DNG photo, then create your own preset from its settings (especially on Lightroom Mobile).

Adobe’s ecosystem supports storing and moving adjustments in different ways (including embedding settings in DNGs or exporting to XMP), which is why the same “look” can travel as a DNG file or an XMP preset file. For the official reference, see Adobe’s guide to managing Camera Raw settings (including XMP and DNG behavior) and Adobe’s overview of the Digital Negative (DNG) format.

Reality check: If you imported a DNG “preset” like an XMP preset, Lightroom may show it somewhere—yet it won’t affect your photos because it was never a real preset file to begin with.

The 60-second diagnosis: is it the preset file, or your Lightroom setup?

Before you change anything big, run this quick test. It saves you a ton of time.

Try a known-working preset (any preset you’ve used before) on the same photo.
Try the “problem” DNG preset on a totally different photo (ideally a RAW file, not a JPEG).
Restart Lightroom and test once more.

If no presets affect the photo, your issue is likely software/caching/preferences or a corrupted catalog/settings state.
If other presets work but that one doesn’t, it’s usually the import method, a missing profile, or a corrupted download.

Most common reasons DNG presets import but don’t change the image

Wrong workflow for the app: Lightroom Mobile DNG packs often require importing DNG “photos” and creating presets from them, not importing as presets.
Version/profile mismatch: The look was built on a profile or process version your app isn’t using (or can’t access).
Corrupted download / incomplete ZIP extract: The DNG opens, but the embedded settings are incomplete or the file is damaged.
Preset applies only subtle changes: Some looks are “soft.” On a photo that already matches the intended baseline, it can feel like “nothing happened.”
Conflicting settings already on the photo: Auto settings, previous edits, synced settings, or copied develop settings can override what you expect to see.
Cache/permissions issues: Lightroom/ACR can behave strangely when it can’t properly read/write its preset/settings folders (especially external drives or locked folders).

The fix-it workflow: step-by-step troubleshooting (start here)

Step 1: Use the correct import method for your Lightroom version

Lightroom (Desktop) / Lightroom Classic: If you have XMP presets, import them properly. Adobe’s official steps are here: Adobe’s guide to installing presets and profiles in Lightroom.

Lightroom Mobile: Most DNG “preset packs” are delivered as DNG images. The common workflow is:

Import the DNG images into your Lightroom Mobile library.
Open one DNG, then use Copy Settings (or “Create Preset” from the menu depending on your version).
Save it as a new preset group (e.g., “My DNG Imports”).
Apply your newly created preset to your own photos.

Adobe Camera Raw (Photoshop): If you’re trying to use presets in ACR, make sure you’re importing supported preset/profile files through the proper menu. ACR’s profile/preset import is covered in Adobe’s Camera Raw documentation (and the folder locations and storage options matter). For the official reference, see Adobe’s Camera Raw settings guide.

Step 2: Re-download the preset pack (and extract it cleanly)

This sounds basic, but it fixes a surprising number of “imports but doesn’t apply” cases.

Delete the non-working preset/DNG files you imported.
Download again from the original source.
Extract with a reliable unzip tool (avoid partial extraction).
Re-import using the correct method for your app (Step 1).

Step 3: Convert a DNG “look” into a real preset (the most reliable workaround)

If your DNG file opens but applying it “as a preset” doesn’t do anything, treat it like a reference edit and build a preset from it.

In Lightroom Classic / Desktop:

Import the DNG file into your catalog.
Open it in Develop and confirm the look is actually applied on that DNG.
In the Presets panel, click + → Create Preset.
Select only the settings you want (start with Tone, Color, HSL, Curves; be careful with Crop, Healing, and Masks unless you really want them included).
Save it to a new preset group and test it on a fresh RAW photo.

In Lightroom Mobile:

Open the DNG “preset” photo.
Tap the three dots menu → Create Preset (or Copy Settings → Create Preset, depending on your version).
Name it clearly (e.g., “Warm Pastel Street – DNG Converted”).
Apply to a new photo and fine-tune exposure/white balance.

This approach bypasses most import quirks because you’re making a native preset that matches your current app version.

Step 4: Check for missing profiles (the “invisible preset” problem)

Some looks depend on a specific profile (for example, a camera matching profile). If that profile isn’t available, the preset can feel like it did nothing—or it applies only part of the look.

In Lightroom/ACR, open the Profile browser and switch between Adobe Color and other profiles to see if the baseline rendering changes.
Re-apply the preset after selecting a stable baseline profile.

Step 5: Reset the photo state before testing

When you’re troubleshooting, you need a clean baseline.

Use a fresh photo with no edits.
If you already edited it, create a Virtual Copy (Lightroom Classic) or “Reset” the edits (Mobile/Desktop).
Turn off any synced settings that might be auto-applying on import.

Step 6: Handle cache and “Lightroom is being weird” glitches

Sometimes the preset is fine, but Lightroom’s cached previews/settings get stuck.

Fully quit Lightroom (not just minimize).
Restart your computer if the problem has been repeating across multiple sessions.
If you use Camera Raw, review its storage behavior (database vs XMP sidecars vs embedding in DNG) in Adobe’s Camera Raw settings documentation.

Step 7: Don’t store presets on an external drive (avoid permissions surprises)

If your preset pack lives on a drive that disconnects, sleeps, or has restrictive permissions, Lightroom can “see” the import but fail to read the settings correctly.

Move the preset/DNG files to a local folder (Desktop).
Re-import from the local drive.
On mobile, ensure files are fully downloaded (not cloud placeholders) before importing.

Step 8: If your preset is extremely subtle, amplify the “proof” test

To confirm whether anything changed at all:

Toggle the before/after view.
Check the History panel (Lightroom Classic) to confirm a preset action is logged.
Look at the curve/HSL panels—if sliders changed, the preset applied.

Step 9: When it’s truly a broken file, use a known-good pack to keep working

If the file is corrupted or packaged incorrectly, don’t lose your editing momentum. Use a reliable set (with both DNG and XMP) so you can keep moving while you replace the bad file. For example:

DNG vs XMP presets: which one should you use?

If you’re deciding what to keep long-term, here’s the practical difference.

XMP presets are cleaner for desktop workflows: they live in your preset library, update nicely, and are easier to back up.
DNG presets are popular for mobile because they can be distributed as “edited DNG photos,” then converted into presets inside the app.

If you want a deeper breakdown (especially for mobile users), this internal guide helps: DNG vs. XMP Presets: a comprehensive guide for Lightroom users.

Presets vs manual editing: the workflow that gives you consistency and control

You don’t have to pick a side. The best workflow is usually “preset + smart adjustments.”

Presets win for: speed, consistency across a shoot, and building a signature look.
Manual editing wins for: mixed lighting, tricky skin tones, and photos that need precise color accuracy.
The sweet spot: apply a preset to get 70–80% of the vibe, then adjust exposure, white balance, and one or two color ranges (often greens and oranges) to finish.

A real-world example: how I troubleshoot “nothing happened” presets in under 3 minutes

I ran into this on a low-light wedding edit where I was moving fast: I imported a DNG look, applied it, and the image barely changed. My fix was simple: I opened the DNG file itself to confirm the look was real, then created a native preset from it. Once I applied the newly created preset to the gallery, it behaved perfectly—because Lightroom was no longer “guessing” how to interpret that DNG package.

I’ve had the same thing happen on travel edits too—especially when I’m switching between Mobile and Desktop. The moment I standardize the format (usually XMP on desktop, DNG-to-preset conversion on mobile), the “silent preset” problem disappears.

Pro tips to prevent DNG preset issues in the future

Build a “baseline preset” first: make a tiny preset that sets profile + basic tone only. Apply it before your creative look for more predictable results.
Fix exposure and white balance before style: presets react best when your photo isn’t wildly under/overexposed.
Avoid stacking heavy presets blindly: stack intentionally (base → look → small finishing preset). If you want a stacking workflow, see how to stack presets for unique and stunning results.
If you changed cameras recently: expect small profile/HSL adjustments. This guide helps: Camera body switcheroo? Here’s how to fix your presets.

Wrapping it up: the simplest “always works” solution

If your DNG presets import but don’t apply, don’t fight the mystery for hours. Use this order: (1) confirm the right workflow for your app, (2) re-download and re-import cleanly, (3) convert the DNG look into a native preset. That sequence fixes the majority of cases.

If you’re ready to edit without worrying about format issues, explore the 1000+ Master Lightroom Presets Bundle (DNG + XMP) and browse the Lightroom Presets for Mobile & Desktop collection. You can also build a full kit faster with the Buy 3, Get 9 FREE offer. If you’re still stuck and want a human to look at your setup, reach out via the AAAPresets contact page.

Why do my DNG presets import but not change the photo?

Most of the time, the file you imported is a DNG “edited photo” meant to be converted into a preset (especially on mobile), not a true preset file like XMP. Re-import using the correct workflow, or create a native preset from the DNG’s settings.

Should I use DNG or XMP presets in Lightroom?

XMP is cleaner for desktop and easier to manage long-term. DNG works well for mobile distribution, but the best approach is converting the DNG look into a native preset inside Lightroom so it behaves consistently.

Why do presets work on one photo but not another?

Different exposure, white balance, file type (RAW vs JPEG), and profiles change the “starting point,” so the same preset can look wildly different. Set a basic exposure/WB first, then apply the preset and fine-tune.

Do DNG presets work in Adobe Camera Raw?

ACR supports presets and profiles, but the cleanest workflow is using XMP presets or converting a DNG look into a preset you can reuse. Also make sure ACR’s settings storage and folders are behaving normally.

What’s the fastest fix if I’m on Lightroom Mobile?

Import the DNG files into your library, open one, then use Create Preset (or Copy Settings → Create Preset). Apply your newly created preset to your own photos instead of trying to “import the DNG as a preset.”

Written by Asanka — creator of AAAPresets (10,000+ customers).