How do you show an image on desktop only in Adalo?
Show an image only on desktop by disabling its tablet and mobile visibility in the responsive Layout tab, then verify the parent group at every breakpoint.
Short answer
In a responsive Adalo app, select the image, open the Layout tab, and turn off visibility for Tablet and Mobile while leaving Desktop on. If the image sits inside a group, check the group's visibility too, because a hidden parent group overrides its children.
The intended outcome
The image appears at Adalo's desktop breakpoint and remains hidden at the tablet and mobile breakpoints.
Use responsive screen-size visibility when the rule depends on the viewport, not on the current user or record. Select the image in the responsive builder, leave Desktop visible, and disable Tablet and Mobile. Then inspect the containing group and preview every breakpoint. This keeps a presentation rule in the Layout tab instead of building a database condition for it.
Requirements
- A responsive Adalo app; the Layout tab is not available in legacy apps
- The image component or its containing group selected in the editor
- Access to desktop, tablet, and mobile preview sizes
Step by step
Step 1: Select the image
Open the responsive screen and select the image component that should appear only on desktop.
Step 2: Open the Layout tab
In the left editor panel, switch to Layout and find the device-size visibility controls at the top.
Step 3: Keep Desktop visible
Leave Desktop enabled, then turn off Tablet and Mobile for the selected image.
Step 4: Check the parent group
If the image belongs to a group, confirm the group is visible on Desktop; parent visibility overrides child settings.
Step 5: Preview all three sizes
Preview desktop, tablet, and mobile widths and confirm the image appears only at the desktop breakpoint.
The underlying logic
Screen Size Visibility is breakpoint-based layout behavior, not a database condition: Desktop starts at 992px in Adalo's current breakpoint model.
Turning off Tablet and Mobile removes the component at those device sizes while preserving the Desktop layout.
A child component cannot display when its containing group is hidden, even if the child's own Desktop toggle is enabled.
Data model
| Collection | Important properties | Relationships |
|---|---|---|
| No database collection required | Image component and device-size visibility settings | None; visibility is controlled by responsive breakpoints |
What still needs checking?
- This answer is forum-native and follows the current responsive Layout tab documentation rather than a legacy Adalocado video.
Common failure modes
Testing checklist
0 of 7 checked on this device
Current limitations
- The official Layout tab workflow applies to responsive apps; the accepted forum reply suggested a third-party component for legacy apps, which this draft does not endorse or verify.
- Adalocado has checked the current public documentation but has not reproduced the workflow or captured a current builder screenshot yet.
What the Adalo community is reporting
These are concise editorial summaries of public forum posts, not endorsements or independently reproduced results.
Affichage images
The accepted answer directs responsive-app users to Adalo's Screen Size Visibility controls and treats legacy apps as a separate case.
Boundary: The forum's third-party legacy-app suggestion has not been independently checked and is excluded from the recommended workflow.
JohnstonB (question) and Dilon (accepted answer) · May 2026
Sources and status
This page was last reviewed on Aug 14, 2026. Its current status is Documented from current sources.
Verification owner: Pending Adalocado screenshot and editorial review. Next review: Oct 14, 2026.
Changelog
Automatically posted from a solved Adalo forum topic; corrections are monitored on the live site.
Automatically organized and maintained by the Adalocado editorial team under the editorial and verification policy.
Report this answer.
Automated Answers still pass evidence and publication checks, but they can be wrong, outdated, unclear, or missing an important boundary. Send the exact correction and the editor will check the live page.
Did this solve your problem?
One-click check
We’ll handle the tech. You can exhale.
Bugs fixed. Updates shipped. Publishing handled.
$97/mo for your first 3 months.
Cancel anytime. That’s about 90% off the usual cost. 🤯
- Bug fixes and troubleshooting
- App updates and integrations
- Publishing and store releases
Bring us the messy version.
Describe what you expected, what happened instead, and what you already tried.
