Public, unlisted, and private image sharing
Choose the right access setting for a portfolio, a group chat, or a private archive. Then test the exact link from the recipient’s side.
2026. 11. 10. 오후 4:07 UTCYou come home from a hike with three plans for the photos. One shot goes into your portfolio, a few go to the group that joined you, and the family pictures stay in your own archive. They all came from the same camera, but each group needs a different audience. Start by asking whether someone who has never received the address should be able to open the picture tomorrow.
When should you share an image publicly?
Public access makes sense for a portfolio image, an event announcement, or a product photo that has been cleared for wide distribution. A visitor should be able to open the image page without using your account. If the same picture will appear in a presentation or on a website, test access to the file and any embedding behaviour from that destination too.
Setting an image to public does not automatically place it in a discovery feed. ImgPage has a separate review and approval step for Discover. Elsewhere, search visibility can depend on links and indexing settings. Think of access as deciding who can open the picture, and discovery as deciding where they might find it.
Who can get an unlisted link?
An unlisted link can be convenient for sharing hiking photos in a group chat. Each recipient receives an address and can potentially forward it, paste it into a document, or pass along the message. Sending a link to six people does not, by itself, tie access to those six identities.
Decide how long the link will be useful before you send it. A short window may be enough for a group choosing favourites over the weekend. Before shortening access, consider whether anyone needs the files later. An expired link can stop opening while copies that were already saved remain on recipients’ devices.
Test private images outside your own account
Choose private visibility for a personal archive, unpublished work, or a file you want to keep restricted. Seeing it in your own dashboard is expected. To check the boundary, open the address in a separate browser profile where you are signed out of the owner account. If the service supports access for specific people, test with both a permitted and an unpermitted account.
When putting together an album, review its cover, the individual files, and any share link as a set. One photo may have been uploaded with different permissions. Opening the album page and viewing every file inside it can be different operations. Remove anything that should stay private and reopen the album from a clean session.
Run a quick rehearsal with the exact addresses
Start with three sample files. Prepare a public page for a portfolio picture, an unlisted album for a trip selection, and a private entry for a personal shot. Open all three in your usual browser. Then try the exact addresses you intend to send from a window where you are signed out. If the image and its page have separate addresses, check whichever ones the recipient will use.
If the same project has a cover and a downloadable file, tell the recipient which one they need. Click the link in the drafted message one last time so you catch any mix-up between similar addresses. After changing access, test the old address the same way. This gives you a result that does not depend on your open owner session or an earlier preview.