
The Your stuff > Lightroom photos integration is documented for the design editor, not the Webpage editor. A webpage has a separate Photo action whose documented sources include Lightroom. Check the editor and entry point before concluding that Lightroom photographs cannot be used in the webpage.
Identify which editor is active
Express supports different creation surfaces. A design canvas and a scrolling webpage do not expose every source in the same panel. Record whether you are editing a design or a webpage and which control you are opening.
Imagine a hypothetical photographer creating a portfolio page after building a social poster. The poster's Your stuff panel offers Lightroom photos; the photographer looks for the same tab in the webpage and cannot find it. Repeated account sign-ins would not address an editor-specific entry point.
Adobe's Add Lightroom photos guide explicitly excludes that integration from the Webpage editor. Its webpage guide separately lists Lightroom among Photo sources.
Use the documented route for the surface
In a design, open Your stuff and Lightroom photos, then choose a recent photograph. In a webpage, use the add-content control and Photo, then inspect the available source choices for the appropriate Lightroom option.
Keep the photograph's identity clear: record the selected image, intended crop and caption. Do not assume that a similarly named thumbnail is the approved export or that inserting an image publishes the page automatically.
If the source option does not appear as documented, note the active editor, account and precise missing control. Avoid generalizing the failure into “webpages do not support Lightroom” when the official webpage instructions describe a separate route.
Review the placed photograph
Check the visible crop, orientation, caption and image quality in the actual page preview. A photograph suitable for a compact social card may not be the appropriate crop for a wide webpage section.
A Photopea document-tab versus canvas comparison illustrates another entry-point distinction. The same source asset can reach different destinations depending on the action selected.
Do not diagnose a browser export restriction as a Lightroom picker issue. A canvas showing an image while blocking export has a separate cause and needs separate evidence.
Accept the published view, not only the source picker
For the portfolio scenario, acceptance means the intended photograph appears with the approved crop and caption in the correct webpage section. Preview the page and check the delivered view through the normal publishing workflow.
If color is disputed, inspect the actual source and output workflow rather than randomly changing profiles. Assigning versus converting a GIMP profile explains why those operations are not interchangeable.
If the integration remains unavailable, use an authorized export or another supported Photo source while preserving the original. State that fallback explicitly instead of claiming the missing tab was repaired.
Related tasks
- Why Can I See a Photo in the Browser Editor but Cannot Export the Canvas?
- Why Did Dropping a Photo into Photopea Add a Layer Instead of Opening a Document?
- GIMP: Assign or Convert an Untagged Adobe RGB Image?
Sources and scope
- Adobe: Add Lightroom photos: Your stuff > Lightroom photos integration is not available in Webpage editor.
- Adobe: Design webpages: Webpage Photo sources include Lightroom; embedded Express video limited to first five minutes.
Documentation-based guidance. Examples are hypothetical and acceptance checks are proposed; no installed-application test is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.