How to Share Images Online From a Website

Short answer: Put the image on a publicly reachable website or image host, then share either the page or album URL (for context and controls) or the direct image URL (when the recipient needs the image file itself). Before sending it, confirm the visibility setting and remember that a link is not strong secrecy.

1. Choose the kind of link you need

Link	Use it when	Trade-off
Website page or post	You want surrounding text, branding, comments, navigation or other controls.	The recipient must open a page before seeing the image.
Album link	You are sharing several personal photos together.	Access and collaborator settings must be reviewed.
Direct image URL	The recipient needs the image resource, an embeddable address or a quick preview.	The file can usually be downloaded and may lose context.

Decide this first. Sending a direct file URL when you need an album’s controls, or sending an album page when someone needs an embeddable image, creates avoidable friction.

2. Publish an image on a website you control

WordPress

Open the Media Library or the editor for the page or post.
Upload the image and wait for processing to finish.
Insert it into the page, add descriptive nearby text and useful alt text, then publish.
Open the published page in a private browser window to confirm that it is publicly reachable.
Copy the page URL. If you need the file itself, open the media attachment or copy the image address provided by your site.

WordPress documents uploading, storing and displaying media in its image and file attachments guide.

Plain HTML site

Upload the file to your site’s public assets directory, reference it from a page, and deploy both files. This minimal example displays an image and gives visitors a link to the original:

<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Project photo</title>
</head>
<body>
  <figure>
    <a href="/images/project-photo.jpg">
      <img src="/images/project-photo.jpg"
           alt="Completed garden project in spring"
           width="1600" height="1067" loading="lazy">
    </a>
    <figcaption>Completed garden project in spring.</figcaption>
  </figure>
</body>
</html>

Use a stable, publicly served path, set width and height to reduce layout shifts, and keep the original file link only if recipients need the full-resolution asset.

3. Upload to an image host

An image host is useful when you do not operate a website or need a quick hosted URL. On Imgur, desktop instructions use New post and let you select or drag in files. After uploading, its help explains how to copy an image address. See Imgur’s upload instructions and URL instructions.

Sign in to the host and upload the image.
Choose the post, album or visibility setting.
Copy the page link for context, or copy the image address for the file.
Open the copied URL in a private window and test it before sharing.

Provider limits and interfaces change. Imgur’s help currently states an upload limit of 50 images per hour; check its current documentation before designing a bulk workflow.

For personal collections, Google Photos supports sharing with selected people or by link. Named-person sharing gives tighter control than a link that can be forwarded. Google explains that turning link sharing off stops access through the old shared link; removing someone from an album alone may not invalidate a link they already have. Review the sharing options and shared-album controls.

Create or open the album.
Choose specific accounts when access should be limited; use link sharing only when forwarding is acceptable.
Copy the album URL and send it through your chosen channel.
When access must end, disable link sharing and review collaborators.

5. Check visibility and privacy before sending

Test anonymously: use a private window or a logged-out browser.
Inspect the destination: verify that the URL opens the intended page or file and uses HTTPS.
Assume links can spread: anyone who receives a link may forward it.
Do not treat hidden as secret: Imgur says hidden posts are not searchable in the same way as public posts, but images remain reachable through direct URLs and can be downloaded. Its privacy help also says uploaded images have EXIF metadata removed. Read Imgur’s privacy guidance.
Remove sensitive metadata yourself: check location, camera and author fields before uploading to any service.
Have a revocation plan: know how to delete the upload, disable link sharing or replace the link.

6. If you want the image to appear in search

Google says an image and its page must be publicly accessible to be considered for Google Images. Add accurate alt text, a useful caption and descriptive nearby copy. Publishing does not guarantee immediate indexing or placement. See Google’s image-search guidance.

If the “image” is a webpage state, you can capture it yourself with a browser. This gives you control over the viewport, timing and output, but you must operate a browser and handle pages that load dynamically.

import { chromium } from 'playwright';

const browser = await chromium.launch();
const page = await browser.newPage({ viewport: { width: 1440, height: 900 }, deviceScaleFactor: 1 });
await page.goto('https://example.com', { waitUntil: 'networkidle' });
await page.screenshot({ path: 'page.png', fullPage: true });
await browser.close();

Browser-capture checklist

Wait for a selector, a known delay or network idle when content is asynchronous.
Set the viewport and device scale factor explicitly so output is repeatable.
Handle cookie banners, newsletter modals and chat widgets before capture.
Set a timeout and record failures; do not publish an empty or partial image silently.
Keep credentials and private headers out of client-side code.

8. Or skip the browser setup

ScreenshotNeo captures a URL with one GET request and returns PNG, JPEG, WebP or PDF. Before capture it accepts cookie and consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and the response identifies the result with X-Page-Verdict and X-Billed headers.

See the ScreenshotNeo API documentation for all options, including full-page and CSS-selector capture, dark mode, device presets, retina scale, custom CSS and JavaScript, clicks, waits, request blocking, headers, cookies, user agents, authorization, timezone, geolocation, transparency, resizing, TTL caching, signed links, asynchronous jobs, webhooks, bulk capture and usage.

cURL

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

Python

import requests

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

Node.js

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://stripe.com'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot failed: ${res.status}`);
const buffer = Buffer.from(await res.arrayBuffer());
require('fs').writeFileSync('shot.webp', buffer);

ScreenshotNeo has a Free plan with 1,000 shots per month and no card. Paid plans start at $5 for 3,000 shots; every feature is available on every plan. Its MCP server also gives Claude, Cursor and other MCP clients take_screenshot, get_page_info and capture_pdf tools. Create a free ScreenshotNeo account.

9. Troubleshooting

Symptom	Likely cause	Fix
Recipient sees “not found”	The URL is private, mistyped or the upload was deleted.	Test while logged out, copy the current canonical URL and check the host’s visibility setting.
Image opens in your account only	Authentication or membership is required.	Publish it publicly or share with the recipient’s account explicitly.
Only a page opens, not the file	You copied an album or post URL.	Use the host’s “copy image address” action when a direct resource URL is required.
Old viewers still have access	A shared link remains active.	Disable link sharing or reset the link, then send the replacement.
Screenshot is blank or partial	The page needs more time, blocks automation or renders after interaction.	Wait for a selector or network idle, trigger required interactions, and inspect the page verdict or browser logs.
File is too large or slow	Original dimensions or format are excessive.	Resize or convert to WebP/JPEG for sharing while retaining the original privately.
Link breaks later	The host changed retention, the post was removed or the path was not stable.	Use a service with documented retention, keep a managed copy and periodically check important links.

10. Performance, reliability and cost

Dimensions: large originals consume more bandwidth and can be slow on mobile. Create a web-sized derivative and keep the original separately.
Format: JPEG suits photographs, PNG suits transparency or sharp interface graphics, and WebP can reduce transfer size when recipients support it.
Caching: stable URLs and cache headers improve repeat views; changing filenames or query strings can defeat caches.
Availability: keep important images on a host you control, maintain a backup and test links from outside your account.
Access costs: check storage, bandwidth, upload and API quotas before automating a high-volume workflow. Free limits and provider policies can change.
Screenshot automation: reuse browser instances, set explicit timeouts and wait conditions, and avoid capturing until the page is ready. With ScreenshotNeo, cache hits and failed or unusable page verdicts are not billed.

FAQ

Should I send a page URL or an image URL?

Send a page or album when context and access controls matter. Send the direct image URL when the recipient needs the image resource itself.

Can a hidden image link be private?

No. A recipient can forward the URL, and direct files can often be downloaded. Use account-based sharing for tighter control.

How do I stop a shared link?

Disable link sharing, delete the upload or reset the link according to the service’s controls. Google Photos documents turning link sharing off to invalidate access through the old shared link.

Why is my image not in Google Images?

Make both the page and image publicly accessible, add descriptive text and wait for indexing. There is no immediate-placement guarantee.

Can I automate webpage images without maintaining Playwright?

Yes. ScreenshotNeo accepts a URL through its API, handles consent and common overlays before capture, and provides options for waits, selectors, devices, output formats and asynchronous jobs.