How to Upload an Image and Create a Shareable Web Link

Short answer: upload the image to a service that hosts files, change its access setting to the people who should see it, choose read-only access when appropriate, and copy the generated link. For a private image, keep access restricted and invite named people. For broad access, use an “Anyone with the link” setting and remember that the link can be forwarded.

The best method depends on whether you need a file link, a photo album, a public image-hosting page, or an automated upload.

Workflow	Best for	Link opens	Main access control
Google Drive	One image file with clear permissions	A Drive file	Restricted or anyone with the link; Viewer, Commenter, Editor
Google Photos	Albums and photo-library sharing	A shared album or photo	Link sharing and collaborators
Imgur	A quick image-hosting page	A post or image-hosting page	Public-post visibility during upload
Google Photos API	Programmatic uploads	A media item in a user’s library	API credentials and library permissions

Method 1: Upload an image with Google Drive

Open Google Drive and select New → File upload.
Choose the image on your computer or phone and wait for the upload to finish.
Right-click the uploaded file and choose Share (or open its sharing controls).
Under General access, choose Restricted for named recipients, or Anyone with the link when every link holder may open it.
Set the role to Viewer unless recipients genuinely need to comment or edit.
Select Copy link and send it through your normal channel.

Google Drive states that the owner’s name and email are visible when a file is shared by link. A shared link is also a bearer credential: anybody who obtains it can use it when general access is set to anyone with the link. Review the parent folder too, because inherited folder permissions can broaden access. Work and school accounts may prevent external sharing. See Google Drive’s sharing guidance.

Make a Drive link private again

Open the file’s sharing dialog, change general access back to Restricted, and remove people who should no longer have access. If the file inherits access from a folder, adjust the folder permission as well.

Upload the photo to Google Photos.
Create or open an album and choose Share.
Enable link sharing if recipients do not need individual invitations.
Copy the album or photo link.

Google Photos is useful when people should browse several photos together. Link sharing has a specific revocation behavior: turning link sharing off and then on again creates a new shared-album URL. Removing a collaborator by itself does not invalidate the old URL while link sharing remains enabled. See Google Photos sharing guidance.

Method 3: Upload to Imgur

Imgur provides an upload-and-share flow for image-hosting pages. During the public-post workflow, choose the intended visibility before uploading, then copy the resulting post or image URL. Check that setting carefully before sharing anything sensitive; a public post may be discoverable beyond the people you intended to reach. Imgur’s help documentation describes the upload and public-post process.

How to choose the correct access setting

Goal	Recommended setting	Why
Only specific coworkers or clients	Restricted + named people + Viewer	Access is tied to their accounts.
Anyone in a project who receives the URL	Anyone with the link + Viewer	No individual invitations are needed.
Collaborative editing	Named people + Editor	Limits editing to identified collaborators.
Temporary access	Share, then return to Restricted	Stops future access after the handoff.
Sensitive or personal image	Restricted	A forwarded URL alone will not grant access.

Security and privacy checklist

Open the link in a private browser window before sending it.
Confirm that the recipient sees only the intended image, not a whole folder or album.
Use Viewer access for ordinary sharing.
Remember that anyone-with-the-link URLs can be forwarded.
Check whether your name and email are exposed by the service.
For Google Photos albums, reset the URL by toggling link sharing off and on when you need to invalidate the old link.
For Drive, inspect parent-folder permissions and organization sharing policies.
Remove metadata from an image before upload if it contains location or device details you do not want to disclose.

Automate uploads with the Google Photos API

The Google Photos API uses a two-step process: upload the file bytes to receive an upload token, then use that token to create a media item in the user’s library. The documented accepted photo types include AVIF, BMP, GIF, HEIC, ICO, JPG, PNG, TIFF, WEBP, and some RAW formats. The API documentation lists a 200 MB maximum photo size; do not generalize that limit to every manual upload path.

Authenticate with the required Google Photos library permissions.
POST the image bytes to the upload endpoint and capture the returned upload token.
Send the token to the media-items creation endpoint with the desired description or album.
Store the returned media-item identifier and apply the sharing workflow supported by the API.

This is more involved than a manual Drive or Photos upload because your application must manage OAuth credentials, retries, token storage, file validation, and API errors.

When a link does not work

Symptom	Likely cause	Fix
“You need access” message	The file is Restricted or the recipient is signed into the wrong account.	Add the recipient’s account, or change general access to anyone with the link.
Link opens a folder or album instead of one image	You copied the parent folder or album URL.	Open the individual image’s sharing menu and copy its link.
External sharing is disabled	A work or school administrator blocks outside sharing.	Ask the administrator, use an approved organization location, or share with internal accounts.
Old Google Photos link still works	Link sharing remained enabled after removing a collaborator.	Turn link sharing off, then on again to reset the album URL.
Upload fails	Network interruption, unsupported format, quota, or file-size limit.	Retry, check the file type and size, verify account storage, and upload a smaller copy.
Recipients see your identity	The service exposes the owner’s profile details on shared files.	Use an account appropriate for the audience and avoid sharing sensitive files through a broad link.
API request is rejected	Missing OAuth scope, expired token, malformed request, or an image over the documented limit.	Refresh authentication, validate the request body, and enforce the 200 MB Photos API limit before upload.

Performance, reliability, and cost considerations

Large files: compress or resize images when recipients do not need the original resolution. Smaller uploads finish faster and use less storage.
Reliable transfers: keep the original until the upload is confirmed, and retry interrupted uploads rather than assuming a copied URL means the file is available.
Quotas: Google Photos storage is shared across Photos, Gmail, and Drive, so existing usage can reduce available space.
Access changes: permission changes can take a short time to propagate. Reopen the link in a private window to verify the effective setting.
Automation: validate MIME type and byte size before sending, use bounded retries with backoff, and record the upload token or media-item ID for recovery.
Cost: Drive, Photos, and Imgur account limits and policies vary. Check the current service terms and your account’s storage before building a workflow around them.

Or skip the browser setup

If your actual goal is to capture a webpage as an image or PDF and receive a file directly, ScreenshotNeo provides a single HTTP request. Its API can return PNG, JPEG, WebP, or PDF, and the documentation lists the available options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing result. Its MCP server lets Claude, Cursor, and other MCP clients call take_screenshot, get_page_info, and capture_pdf. One thousand screenshots per month are free with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.

FAQ

Can I make a link without uploading the image?

No. A link must point to a hosted file, album, post, or API resource. Upload first, then configure access and copy the resulting URL.

Should I choose Viewer or Editor?

Choose Viewer unless recipients must change the file or its contents. Editing access is broader than ordinary image viewing.

Is anyone-with-the-link private?

No. It removes the need for individual invitations, but anyone who obtains the URL may be able to open it.

How do I stop a shared Google Photos album link?

Turn link sharing off and then on again. The new link replaces the old shared-album URL.

What is the Google Photos API size limit?

The documented API guide lists 200 MB for a photo. That figure applies to the API documentation, not necessarily to every manual upload route.