Participant

Question

Lightroom Classic .webp Import Celebration

Forum|Forum|1 month ago
February 24, 2026
5 replies
211 views

It is important that I mark this event in the annals of the Adobe Community. Today I imported my first ever web-pee file. This happened, almost without warning, after years of screaming for this capability by near-death boomer users of Lightroom Classic.

Attached is the actual image file that I imported today. I appropriated the photo from Google Images and will be exploiting it for my own purposes (now that I can find it again).

I have to ask what took so long to implement this seemingly simple thing? And why all the development time spent on Develop module? How many aged LRC users do not use Photoshop? All but one? Is the one still even with us?

For my last wish, why not make something akin to AnyFile plugin an integral part of LRC? I am lifetime user of AF, but the fake image file thing is laborious and prone to human error. Firefly could analyze my audio files, for example, and produce a thumbnail preview file without having to build a network of AI satellites in space. Can we at least agree on that?

I am not even going to proof this post because it is just that inane. Thank you for storing this message forever.

(see metadata for credits)

G

gormik

Participant

I deliver almost only webp along with master files. I want to switch from Lightroom now, what do you recommend have webp export? I really love Lightroom, but now is time to quit.

.random..

Inspiring

I don’t think it makes sense to leave Lightroom Classic just because of this. Despite its flaws and some long-standing gaps, it’s still extremely useful.

I also don’t understand why Adobe still hasn’t added proper WebP export to the workflow. And honestly, I don’t understand why it still can’t read PSD files properly without Maximize Compatibility enabled. But until they fix it, you can solve it with a folder action and a simple script.

That’s exactly what I do: I export from Lightroom into a specific folder, and it automatically converts everything to WebP (sRGB, quality 90) right away.

Yes, there are alternatives, but each loses something. Lightroom Classic is still unusually strong because it combines raw processing, cataloging, metadata, batch work, and a very mature overall workflow in one application.

Camera Raw is not a real substitute for that, since it is mainly just the processing engine. ON1 Photo RAW and ACDSee can replace parts of the workflow, but neither really matches Lightroom in the same overall balance. That is why using a hot folder for extra conversions is often the smarter solution: you keep Lightroom for what it does best, and let the folder automation handle the rest. It is actually a very efficient workflow

If you'd like me to send you the script, let me know.

G

gormik

Participant

Thanks for the tip for folder action! I would really like the script 🙌 → hei@goran.no

ouiouiphoto

Known Participant

As a photographer, importing WebP is useless for me. What I need is exporting WebP to export my photo to use on my website. But importing into my catalog an image grab on the Internet that is not mine is not needed for me. Hopefully I have a WebP droplet i call from LrC to export in WebP

.Sheepdog trying to help Lightroom and Photoshop beginners

.random..

Inspiring

WebP support in Lightroom (Open/Edit/Sync) is a great step — thanks. But without WebP export it’s only half a solution: I have to export to PNG (to avoid quality loss) and then batch-convert to WebP in Photoshop via actions/scripts. Please add native WebP export to LR/LrC and make it available in Bridge and Photoshop too (including Photoshop Image Processor).

More broadly: please fix the inconsistent export feature set across apps. Right now each app can do only part of the pipeline. There’s no good reason export settings/format support should differ between Lightroom, Bridge, and Photoshop. Ideally, reuse Lightroom’s Export UI/options everywhere (format options, metadata handling, resizing, sharpening, and the smart renaming features) so the workflow is consistent and predictable.

Second major pain point: Bridge/LR still depend on the PSD “Maximize Compatibility” composite. When it’s missing, entire archives/workflows break. Please add detection + one-click repair (“This PSD lacks compatibility data — re-save now?” / batch fix) and make compatibility re-saving reliable when the setting is enabled.

Ian Lyons

Community Expert

No doubt some are happy to see support for WebP. However, I wonder how many will remain happy when they realise that support does not extend to being able to export files as WebP.

dj_paige

Legend

This happened, almost without warning, after years of screaming for this capability by near-death boomer users of Lightroom Classic.

No need to call people “near-death”. Offensive post in many ways.

I have to ask what took so long to implement this seemingly simple thing?

I’ll list two possible reasons, you can pick the one you like (and there are probably other reasons):

Adobe programmers are really really really slow, an indication that Adobe programmers are borderline incompetent (which seems to be what your question implies)
It was low on Adobe’s priority list, and just lately it has risen to near the top of the priority list.

Marc_MieherAuthor

Participant

I was talking about myself and I am glad you are offended.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded