Capturing Visual Context

HTML Context Resources

Most websites and web applications are much more than just a single HTML file. Many HTML pages reference other files, such as images, CSS, JavaScript, fonts, etc. to make up the entire page. To display the entire page as visual context to translators, Smartling must fetch and store these referenced files, known as context resources.

You can view the context resources of any HTML context file by clicking Actions > View Resources.


When the HTML file contains accurate and accessible context resources that are under 50 MB, the entire context file displays to translators in the CAT Tool. However, if any of the resources are blocked, the "Resources missing" flag will appear for your attention.

Resources Missing in Visual Context

The "Resources missing" flag appears when the HTML context file contains context resources that have been blocked for any one of a number of reasons.

To address this issues, click the flag to view all context resources within the HTML file in more detail.


Resources dialog lists all context URL's referenced within the HTML file, as well as when it was uploaded to Smartling, updated, and it's current state.

Any URL in a STORED state means that it has been ingested successfully, and can be viewed by translators in the CAT Tool.

Any URL in a MISSING or FAILED state means that it has been blocked from being ingested into Smartling for some reason.




You can choose to ignore any missing resources so that Smartling will no longer attempt to ingest this context file by clicking Ignore.


If you modify any stored resources on your source website, you can update this file in Smartling by clicking Update. This clears any cached outdated context and ensures that the latest version of the file is displayed in the CAT Tool.

Reasons for the Error

Network Issues

The location of the file has blocked our server's IP address. Smartling sends thousands of requests per second. Some servers may flag the Smartling IP and block it from requesting the image file.

The image file, linked within the HTML, lives in a private environment. This could mean that the image is stored within a staging environment, or requires authentication to access it.

Another cause could be SSL restrictions.

The image URL is incorrect

A common cause of this error is when the file lives in a HTTPS domain, but the HTML file contains a HTTP domain location.

The resource is too big

The max size for any visual context resource is 50 MB.



Always ensure images live in an accessible environment, i.e. Production, without authentication, or SSL restrictions.

Check the image link

Ensure the image link on the HTML file is accurate.

Was this article helpful?