Video plays but seeking behaves badly
A video opens, but jumping to another part of the timeline behaves strangely or restarts playback. Check the URL response and range behaviour before assuming the video player itself is the problem.
MEDIA LINK DIAGNOSTICS & TROUBLESHOOTING
Media Link Doctor for URL validation, CORS and stream testing
A media URL can open normally in one browser tab and still fail inside a website, video player or app. The problem may be the server response, a redirect, the reported content type or the way the file is being requested from another origin.
Media Link Doctor helps you inspect the URL before you start changing the code around it. The diagnostic can show the response details available for that request and help narrow down where the media delivery is going wrong.
The workflow
How Link Doctor analyzes your URLs
Start with the exact media URL that is failing where you plan to use it. Testing another copy of the image or a different URL may hide the problem you are actually trying to find.
Link Doctor brings the available response details into one place so you can check the URL itself before spending time changing the surrounding website or application.
1. Test the exact media URL
Paste the reachable image, video, audio or other supported media URL that is causing the problem. Use the same address that your website, player or application is trying to load.
2. Check the server response
Run the diagnostic to inspect the HTTP response details available for that URL. This can include the response status, redirects, headers and range behaviour where those checks are supported.
3. Find the likely failure point
Review the result for problems around status codes, redirects, content type, cross-origin access and media range requests. One failed check does not always mean the file itself is broken, so look at the result in the context where the URL is being used.
4. Decide what needs changing
Use the diagnostic to work out whether the problem belongs to the URL, the source server or the way another site is using the media. If a supported Media2URL import or re-hosting option is available, treat that as a new delivery path rather than a repair to the original external server.
Diagnostic fundamentals
One media URL can fail for several different reasons
A failed image or video does not always mean the file has disappeared. One server may return a redirect, another may report the wrong content type and another may block the way a browser application is trying to use the response.
Checking these problems separately makes troubleshooting much easier than treating every failed media embed as the same issue.
Initial status check
Start with the HTTP response
Before checking CORS or video playback, find out whether the URL is returning a usable response at all. A missing file and a working file with the wrong headers are completely different problems. Link Doctor shows the response status available for the tested request.
| Response | What it usually tells you to check |
|---|---|
| 2xx | The server returned a successful response |
| 3xx | The request is being redirected |
| 404 or 410 | The requested media is missing or no longer available |
| 401 or 403 | Access or authorisation may be blocking the request |
| 5xx | The source server failed while handling the request |
A successful status is only the beginning. The file can still have a content-type, CORS or delivery issue that matters to the destination where you are using it.
Check range behaviour for larger audio and video files
A media player may request only part of a large video or audio file instead of retrieving the complete file every time. When the server supports that request, partial delivery can be part of normal playback and seeking behaviour.
Link Doctor can inspect the available range response where that check is supported. Treat it as one part of the diagnosis rather than a simple rule that every working media URL must always return the same status.
A full response and a partial response are not the same request
A normal request can return the complete file. A range request asks the server for a particular portion of that file instead.
When the server honours the partial request, the response can use 206 Partial Content. This becomes useful to inspect when a large video plays but seeking or partial retrieval behaves strangely.
Check cross-origin access when the media is used by another website
An image may open normally by itself but behave differently when JavaScript or another website tries to use it from a different origin. In that situation, the server's cross-origin response can matter even though the media file still exists.
Link Doctor can show the relevant CORS response information available for the tested URL (Access-Control-Allow-Origin). This is especially useful when a browser application or canvas workflow needs access to the media response.
CORS and hotlink protection solve different problems
CORS controls how browsers handle certain requests between different origins. Hotlink protection is a hosting rule that may restrict where another website is allowed to request or display a file based on referrers.
The two can produce similar-looking failures even though the reason is different. Check what the server actually returns instead of treating every blocked external image as a CORS problem.
Check what type of file the server says it is returning
A URL ending in .mp4 or .jpg does not guarantee that the server reports the matching media type. The HTTP response includes a Content-Type value that tells the browser what kind of content it received.
If that value does not fit the actual file or expected use, another system may handle the URL differently. Link Doctor exposes the reported content type so you can compare it with the media you expected.
Why a file can download instead of opening normally
Content type is not the only response detail that can affect what the recipient sees. A server can also tell the browser to treat the response as a downloadable attachment instead of normal inline content via Content-Disposition: attachment.
If a media URL unexpectedly starts a download, check both the reported content type and the content-disposition behaviour before changing the filename or extension.
Follow the URL when it redirects somewhere else
The URL you paste may not be the address that finally serves the media. A redirect can send the request to another location before the file is returned.
One redirect can be normal. A long chain or loop makes troubleshooting harder because the failure may happen after the original URL has already sent the request elsewhere.
HTTPS problems belong to the source host
A media URL can also fail before the file is returned if the HTTPS connection itself has a certificate or connection problem.
When that happens on an external host, changing your embed code will not repair the source server. The hosting configuration needs to be corrected where that URL is served.
Link Doctor diagnoses the response. It does not rewrite another server.
If an external host returns the wrong header, blocks a request or no longer has the file, Media2URL cannot silently change that third-party server's configuration.
Link Doctor shows what it can observe from the URL and helps you narrow down the likely problem. If you have a working copy of the media and decide to host it through Media2URL instead, that creates another delivery URL rather than repairing the old host.
Re-hosting and repairing are different actions
Suppose an image still exists somewhere you can access, but the old host no longer serves it in the way your website needs. Moving your own supported copy to Media2URL can give you another hosted URL that you control through the Media2URL workflow.
The original external URL does not change because of that upload. Use this option only for media you are allowed to copy and host.
Troubleshooting framework
What should you check first?
| Problem you see | Start by checking |
|---|---|
| The URL shows an error | HTTP status |
| The request keeps moving elsewhere | Redirect path |
| Video seeking behaves badly | Range response |
| Image fails in canvas or scripted use | CORS response |
| File downloads unexpectedly | Content-Type and Content-Disposition |
| HTTPS URL cannot be reached correctly | HTTPS or certificate result |
| Link works in one place but not another | The exact request context and server response |
| Source is permanently gone | Another valid source or a new upload |
Practical scenarios
Real diagnostic scenarios
Image opens directly but fails in a canvas
Opening an image in its own tab only proves that the file is reachable in that context. A canvas or scripted request from another origin can have different cross-origin requirements.
Media downloads instead of opening
The file exists, but opening the URL starts a download instead of the behaviour you expected. Check the content type and content-disposition response before assuming the file extension is wrong.
An old embedded image has stopped working
Start with the current HTTP response. A missing source, redirect, blocked request or changed server configuration each needs a different fix.
Who Link Doctor is useful for
- Developers checking why a media URL behaves differently inside a website, player, canvas or application.
- Website owners testing important image, video or audio links before relying on them in a live page.
- Support teams investigating a broken-media report before escalating it to a developer or hosting provider.
- Content and marketing teams checking important media links before a page, document or campaign is published.
Diagnostic boundaries
What Link Doctor can and cannot see
Link Doctor can only inspect the response it is actually able to reach. A URL that works because your browser already has a private login, VPN or another authenticated session may not return the same result to an external diagnostic request.
Running the test does not change the configuration of the original hosting server. The result reflects the response available at the time of testing, so it can change later if the source server changes.
If the original URL permanently points to a file that no longer exists, testing it cannot bring that missing resource back. You will need another valid source if the media should be hosted again.
Test the URL that is actually failing
A small difference in the URL can send the request through another redirect, transformation or access rule. Testing the original image while your website uses a transformed version may therefore give you the wrong answer. Copy the exact value from the failing page.
Diagnostic questions
Frequently asked questions
The server response can influence how the browser handles the file. Check the reported Content-Type and whether the response is being treated as an attachment via Content-Disposition: attachment. Do not assume the filename or extension alone controls the behaviour.
The file may still exist and open directly. The problem can appear because another website or browser script is trying to use the response across origins without the required permission. Check the cross-origin response for the exact failing URL.
Link Doctor can diagnose response problems, but it cannot rewrite an external hosting server that Media2URL does not control. If a separate Media2URL upload or import option is available, that can create another hosted URL rather than repairing the original one.
The current Media2URL feature page lists Link Doctor as a free diagnostic tool for supported external and hosted media URLs. Check the live tool for any current usage limits or account requirements.
It is a response used when a server successfully returns only the requested portion of a file rather than the complete resource. Range behaviour can be useful to inspect when troubleshooting video or audio playback and seeking.
Opening the URL directly and using it inside another website are different request contexts. The website may depend on cross-origin permission, content type, redirects or another response detail that does not matter when you simply open the file in a new tab.
No. A successful status tells you that the server returned a successful response, but that response can still have a content-type, cross-origin or delivery behaviour that does not fit the way you want to use the media. Treat the HTTP status as the first check rather than the whole diagnosis.
Only when the diagnostic service has a supported way to reach that protected resource. A URL that works because your browser already has a private session or VPN connection may not be reachable in the same way by Link Doctor. Use the result shown by the live tool for the exact URL you are testing.
Related tools