# Expand title image in desktop mode
**URL:** https://community.glideapps.com/t/expand-title-image-in-desktop-mode/69582
**Category:** Ask for Help
**Created:** [January 15, 2024, 2:43pm UTC](https://community.glideapps.com/t/expand-title-image-in-desktop-mode/69582 "2024-01-15T14:43:42Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Gish04](https://community.glideapps.com/u/Gish04)
#### Post date: [January 15, 2024, 2:43pm UTC](https://community.glideapps.com/t/expand-title-image-in-desktop-mode/69582/1 "2024-01-15T14:43:42Z")
Hi all,
Is there a way to get a title image to expand the entire length of the screen in desktop mode? It looks great in mobile but odd in desktop.
---
### Author:  [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)
#### Post date: [January 15, 2024, 3:28pm UTC](https://community.glideapps.com/t/expand-title-image-in-desktop-mode/69582/2 "2024-01-15T15:28:50Z")
How about an image component instead?
---
### Author:  [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)
#### Post date: [January 15, 2024, 4:10pm UTC](https://community.glideapps.com/t/expand-title-image-in-desktop-mode/69582/3 "2024-01-15T16:10:32Z")
Exactly. Use Image component. The problem is that when you search “image” in the list of components, the `title -> image` component is the first one that pops up.
---
### Author:  [@Gish04](https://community.glideapps.com/u/Gish04)
#### Post date: [January 16, 2024, 12:31pm UTC](https://community.glideapps.com/t/expand-title-image-in-desktop-mode/69582/4 "2024-01-16T12:31:57Z")
I might be missing something, but the image component doesn’t fill the mobile space from the edge to edge like the title–\>image component.
---
### Author:  [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [January 17, 2024, 12:49am UTC](https://community.glideapps.com/t/expand-title-image-in-desktop-mode/69582/5 "2024-01-17T00:49:44Z")
So title works for mobile, and image works for desktop?
Perhaps you can use a get device info column to know the type of device the user is using (through device’s width), and display the components accordingly. Group them into containers so it’s less work for you.
---
### Author:  [@Trav\_Cook](https://community.glideapps.com/u/Trav_Cook)
#### Post date: [February 21, 2024, 7:56am UTC](https://community.glideapps.com/t/expand-title-image-in-desktop-mode/69582/6 "2024-02-21T07:56:18Z")
Not sure if this option would work for users that aren’t signed in is that correct? Where would you store the device info if the user isn’t using a user profile?
Maybe there are ways?
I feel like the point is that the ‘Title - Image’ component has a particular look to it that is nice - it goes right up to the top and creates a nice banner for the page - however when switched into desktop viewing mode it seems to loose that look & feel entirely, and rather than attempt to replicate it in some way for a larger device it doesn’t even show the image in full-screen.
So I guess the question would be for the developers - what is that desktop view mode actually trying to achieve for that component when it’s nothing like the original and I don’t know who would want their page to look that way in a desktop view. Maybe it’s meant to be used for something that I don’t understand?
---
### Author:  [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [February 21, 2024, 8:03am UTC](https://community.glideapps.com/t/expand-title-image-in-desktop-mode/69582/7 "2024-02-21T08:03:27Z")
> [@Trav\_Cook](#):
>
> Not sure if this option would work for users that aren’t signed in is that correct? Where would you store the device info if the user isn’t using a user profile?
You can just store it on the row the user is viewing. It doesn’t have to be a user profiles row, it’s just more convenient to store there if your users do log in.
---
### Author:  [@Gish04](https://community.glideapps.com/u/Gish04)
#### Post date: [February 21, 2024, 12:33pm UTC](https://community.glideapps.com/t/expand-title-image-in-desktop-mode/69582/8 "2024-02-21T12:33:31Z")
Thank you for doing a better job of articulating this that I did, Trav. You’ve nailed the problem. I haven’t seen a good solution… other than saying the app is ‘best experienced’ on a mobile device.