Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
DEPRECATED: Prior to recent developments with the picture element, Foresight.js gaves webpages the ability to tell if the user's device is capable of viewing high-resolution images before the image is requested from the server. Additionally, it judges if the user's device currently has a fast enough network connection for high-resolution images.…
JavaScript CSS
tree: 365948a461
Failed to load latest commit information.
demos Added the ability to specify an aspect ratio instead of height and wi…
LICENSE-MIT.txt added MIT License updated references to the data-high-resolution-src attribute
foresight.min.js added foresight.resolve() method and test page


Foresight.js gives webpages the ability to tell if the user's device is capable of viewing high-resolution images (such as the 3rd generation iPad) before the image has been requested from the server. Additionally, it judges if the user's device currently has a fast enough network connection for high-resolution images. Depending on device display and network connectivity, foresight.js will request the appropriate image for the webpage. By customizing the img src attribute using methods such as URI templates, or finding and replacing values within the URI, it is able to form requests built for your image's resolution variants. Media queries however, could be used when dealing with CSS background-images, while foresight.js is used to handle inline img elements (or until current web standards are improved).

Foresight.js has made significant improvements over its previous versions, specifically the implementation of the CSS image-set() function. The latest version lets the browser take control of the image's browser dimensions completely, while the original foresight.js release only worried about which image to request according to the network connection and device pixel ratio. Additionally, foresight.js was previously centered around requesting dynamically sized images, and while this is still possible, it also ensures its easy to request static based images (such as images with "_2x" or "-highres" in the filename). For a more in-depth write-up on foresight's concept please review my article: Using CSS to control image variants.

This project's overall goal is to tackle these current issues faced by web developers designing for hi-res: Challenges for High-Resolution Images. Foresight.js aims at providing a lightweight, cross-browser and framework independent tool for a high-resolution web. Please feel free to contact me (@adamdbradley) or contribute to this project to help improve it.


  • Request hi-res images according to device pixel ratio
  • Estimates network connection speed prior to requesting an image
  • Allows existing CSS techniques to control an image's dimensions within the browser
  • Implements image-set() CSS to control image resolution variants
  • Does not make multiple requests for the same image
  • Javascript library and framework independent (ie: jQuery not required)
  • Image dimensions set by percents will scale to the parent element's available width
  • Default images will load without javascript enabled
  • Does not use device detection through user-agents
  • Minifies to 7K


Before we get too far into the nitty-gritty, it's probably best to view foresight.js in action. Currently most desktop and laptops do not have high-resolution displays and are limited to a device pixel ratio of only 1, so you will not be able to see the effects on a standard monitor. Make sure you view the demos from multiple devices, such as your mobile phone, tablet and traditionalcomputer .

Img Element

One of the largest problems faced with dynamically deciding image quality is that by the time javascript is capable of viewing an img in the DOM, the image file has already been requested from the server. And on the flip side, if img elements are built by javascript then search engines probably won't view them and browsers without javascript enabled will also not be able to view the images. To overcome both of these challenges foresight.js uses the img element, but without the src attribute set, and a noscript element with a child img element.

<img data-src="imagefile.jpg" data-width="320" data-height="240" class="fs-img">
    <img src="imagefile.jpg">

Notice how the first image is missing the src attribute, but instead has a data-src attribute. Because this img element does not have the src attribute the browser will not attempt to download the file. Once the DOM is ready, foresight.js does its magic to transform the data-src and set the src attribute tailored to the device's display and network connectivity. Using this structure allows us to still place img elements within the context of the webpage, while also allowing search engines and javascript disabled browsers to view the images.

One concept change is that both the data-width and data-height attributes should not be seen as the image's physical dimensions in the traditional sense, but rather a way for the browser to know the image's aspect ratio as its size is scaled up and down. Foresight.js decides the image's actual dimensions, while the data-width and data-height attributes help to maintain its correct aspect ratio.

Until the web community completes a new standard to hi-res context images, and it becomes widely adopted by all the major browsers, and the updated browsers are installed on the billions of devices in the world, the approach by foresight.js is one of the few that answers each of the Challenges for High-Resolution Images.

There is hope however as the web community continues to work on a solution for high-resolution images. These resources offer a glimpse about what's currently being worked on (and be sure to read the comments too) Adaptive Image Element, Polyfilling picture without the overhead and The image-set() function (for responsive images).

High-Speed Network Connection Test

Currently most devices capable of hi-res displays are mobile devices, such as new iPhones or iPads. However, since they are "mobile" in nature and their data may be relying on cell towers, even if the device has a hi-res display, users with slow connectivity probably do not want to wait a long time while images download. In these cases, foresight.js does a quick network speed test to make sure the user's device can handle hi-res images. Additionally, it stores the devices network connection speed information for 30 minutes (or is customizable to any expiration period you'd like) so it does not continually perform speed tests. You can host your own speed test file to be downloaded, or you can use the default URI available for public use found in the foresight.js configuration.

Other speed test notes:

  • If the response takes longer than it "should" take to download the test file, then foresight.js will not wait any longer on the test response and automatically consider the connection "slow"
  • If the device has a pixel ratio of 1, then the display in unable to view hi-res anyways. In these cases (which is just about all traditional computers at the moment), it doesn't bother doing a speed test because it already knows its a waste of time since the display can't view hi-res.
  • If the device implements navigator.connection.type, and the known connection type is either 2g or 3g, then it doesn't bother doing the speed test since it already knows its too slow. Android currently seems to be the only one implementing navigator.connection.type, and even then it may not always have the info (but when it does the info save us time, and for 2g that's pretty valuable info).
  • Foresight's publicly available speed test file is hosted by Google App Engine, which is a cloud-based service.
  • If the page requesting the speed test is SSL, foresight.js will ensure the speed test image is downloaded using the https protocol.

CSS: Using image-set() to control image requests

The first version of foresight.js was a proof-of-concept largely using javascript options and HTML attributes. While it showed potential, an area for improvement was to allow many of its features to be controlled with CSS. Its no secret that presentation should be separated from functionality.

The largest introduction is the use of the image-set() CSS function. The image-set() function (for responsive images) thread offers some great insight and direction that responsive images may be heading.

Quote from Edward O'Connor, image-set() function (for responsive images):

I'd like to propose a new function for the Images module. This function will allow developers to provide, in a compact manner, multiple variants of the same image at differing resolutions. Using @media pushes the two asset references apart from one another, whereas such a function keeps related asset references together. It also helps keep selectors DRY. We've called it image-set(), and it takes one or more image specifiers.

Here is an example of a proposed format:

image-set( url(foo.png), url(foo_2x.png) 2x high-bandwidth )

As pointed out, the image-set() function is great because it keeps everything together, which might just be a huge piece of the hi-res puzzle. But obviously this new concept is a ways away from being standardized and widely adopted across the worlds browsers.

The latest version of foresight.js is combining its original idea from the first version, which is the use of URI templates and URI find/replace, and applying them to the image-set() concept. This way you can use just one, or any number of CSS rules to control images throughout your site instead of creating a CSS rule for every image. Check out the URI Template and URI Find/Replace sections for more info.

The basic format is that the image-set() function can contain one, or many, image-set variants, each separated by a comma. Each image-set variant can have up to three arguments:

  1. url(*): Similar to the background-image url() function, the image-set url() function contains a URI to the image to download. What's different, however, is that the image-set url() can contain an actual URI, a URI templates, or a URI Find/Replace. Check out the URI Template and URI Find/Replace sections and examples for more info.
  2. Scale Factor: The scale factor argument is used as a multiplier for the image's dimensions. If an image has a browser width/height off 100x100 pixels, and the applied scale factor is 2x, then the requested image size would be 200x200 pixels. If a device has a pixel ratio of 1.5, and there is no image-set variant with a 1.5 scale factor, then it will round up and use and image-set variant with scale factor of 2.
  3. Bandwidth: The bandwidth argument can either be 'low-bandwidth' or 'high-bandwidth'.

A common format is to set the first image-set variant as the default, and the second image-set variant as the one which gets applied to a device with a pixel ratio of 1.5 and a high-bandwidth. The example below is basically saying, if this device has a pixel ratio of 2 (which includes pixel ratios of 1.5), AND this device has a high-bandwidth, then apply the second image-set variant to this image. However, if this device does not have a high-resolution display, OR it does not have a high-bandwidth, then go with the default image-set variant, which happens to be the first one in the list.

image-set( url(foo.png), url(foo_2x.png) 2x high-bandwidth )

The big hang-up at the moment would be that most browsers have no clue what image-set() is, and since any custom CSS property isn't valid, then the DOM is unable to view this newly introduced image-set() CSS.

Enter font-family!

"FONT FAMILY! FOR AN IMAGE?!? YOU NUTS!" Yes, but hang with me. An img element doesn't use the font-family property because you're not exactly assigning "Times New Roman" to your cat photos, so its already useless to the img element. Secondly, font-family is one of the few CSS properties which lets you enter free-text in the value and the browsers still consider it valid, which makes the value viewable by the DOM and javascript (yup, even IE doesn't care). I completely agree with what your thinking, but please read on and view the demos to see what this method is able to pull off.

In the example below you'll see we're using the font-family property to hold the image-set value. Foresight's javascript is then able to view your image-set() CSS, whether its in an external stylesheet, internal styles within the head element, or even inline styles, and request the appropriate image given the device's circumstances. The example below shows how the image-set() value is assigned to the font-family.

    .fs-img {
        font-family: ' image-set( url(/images/foo.png), url(/images/foo_2x.png) 2x high-bandwidth ) ';

This is good, except now my CSS class fs-img only lets me request the image variants of foo.png and foo_2x.png. However, we'd rather not create a CSS rule for each image on the page.

And I know you may be hung up on the font-family property, but until a better idea comes around its a workable solution for all of today's browsers. Ideally a new or existing CSS property will be able to contain the image-set() values. Using CSS to control image variants.

Now let's take this one step further and allow each image-set variant's url() to have its own URI template, such as:

    .fs-img {
        font-family: ' image-set( url({directory}{filename}.{ext}), url({directory}{filename}_2x.{ext}) 2x high-bandwidth ) ';

This time we're not specifically hard-coding the foo.png file, or even files in the /images/ directory. Instead we're simply stating, "hey browser, if this image should be low-res, then use the first URI template. If this image should be hi-res, then use the second URI template." The URI template informs foresight.js how to parse apart and reconstruct the image request instead of specifying a specific file to request.

Values within url() can be fully customized to your website's image request format, and can contain a URI template or a URI find/replace value. In the example above, any images which have the fs-img CSS classname assigned is provided with two URI templates it could use, but foresight.js chooses which template to use depending on your device pixel ratio and network connection speed. If you view the demos you'll see that the image-set() CSS actually gives you a large array of options, and can be applied no differently than any other CSS rule.

NoScript Element

Immediately you'll notice that HTML structure also includes a noscript element and has a child img element. Obviously this is redundant, but with today's standards this is one of the issues we'll have to dance with. However, if your website has no reason to care about SEO or support browsers without javascript than feel free to omit the noscript elements and display:none CSS all together.

If javascript is not enabled then the browser will show the noscript img instead. In this case the webpage should also hide the foresight.js img so it's not seen as a broken image (since it doesn't have a valid src attribute). The CSS rule applied to foresight.js images should contain the display:none CSS property, such as:

    .fs-img {
        font-family: ' image-set( url({directory}{filename}.{ext}) 1x low-bandwidth, url({directory}{filename}_2x.{ext}) 2x high-bandwidth ) ';


<img data-src="/images/imagefile.jpg" data-width="320" data-height="240" class="fs-img">
    <img src="/images/imagefile.jpg">

When foresight.js executes, it will change each image's display style to 'inline' so the foresight.js images can be seen.

Src Modification

An img src attribute needs to be modified so the browser can request the correct image according to the device and network speed. How an image's src is formatted is entirely up to the URI format of the image's server, but foresight.js allows the img src attribute to be customized to meet various formats.

Src modification can be applied using a few different methods:

src-uri-template: Rebuild the src by parsing apart the current URI and restructure it using the supplied URI template. Review the URI Template section and examples to see how to format the image-set() url values.

src-find-replace: The current src may already have dimensions within the URI. Instead of rebuilding the src entirely, just find and replace the original values within the URI the new values. Review the URI Find/Replace section and examples to see how to format the image-set() url values.

src-hi-res: The data-high-resolution-src attribute can be used to identify which src to use when the device is hi-res ready. See the definition under the Img Attributes section to read more about manually setting which file to use when the hi-res image should be shown instead. The first two Src Modification types should be used when dynamically building the img src, while the data-high-resolution-src attribute is used if you want to manually tell foresight.js which image to use when hi-res is enabled.

URI Template

The src URI template provides foresight.js with how the request should be built for the image. Each server's image request is different and the URI template can be customized to meet each server's format. Below are the various format keys that are used to rebuild the src to request the correct image from the server. Each one is not required, and you should only use the format keys that help build the src request for the server.

{src}: The original src value. Use this if you do not want to make any changes to the src from the one already supplied in the data-src attribute. This would be used mostly for the 1x scale factors and low-bandwidth image-sets, mainly stating that the default image should be requested instead of modifying the src. This is also useful if you are adding querystrings at the end of the original src.

{protocol}: The protocol of the request. ie: http or https

{host}: The host. ie: or

{port}: The port number, but production systems will rarely use this. ie: 80

{directory}: The directory (folder) within the path. ie: /images/

{file}: Includes both the file name and file extension of the image. ie: myimagename.jpg

{filename}: Only the file name of the image. ie: myimagename

{ext}: Only the file extension of the image. ie: jpg

{query}: The querystring. ie: page=1&size=10

{scale}: The exact scale factor for the image to load. This value will automatically be calculated, it's just that you may need to tell foresight.js where to put this info within the src. ie: 2

{scaleRounded}: The rounded scale factor for the image to load. Retina displays are known for having a device pixel ratio of 2, but many others may manufactures could have 1.5 as the pixel ratio. In this case, a pixel ratio of 1.5 will be rounded to a value of 2. This value will automatically be calculated, it's just that you may need to tell foresight.js where to put this info within the src. ie: 2

{requestWidth}: The request width of the image to load. This value will automatically be calculated, it's just that you may need to tell foresight.js where to put the natural width within the src. ie: 320

{requestHeight}: The request height of the image to load. This value will automatically be calculated, it's just that you need to tell foresight.js where to put the natural height within the src. ie: 480

Again, not all of these keys are required inside your template. URI template is entirely dependent on how the server handles image requests. See Server Resizing Images for more information on a few options for requesting various images sizes from a server.

URI Template Examples

Example A: Custom terms within the URI
Original Src:     /images/funnycat.jpg
Uri Template:     url({directory}{filename}-hi-res.{ext})
Request Src:      /images/funnycat-hi-res.jpg

Example B: Scale factor in the filename
Original Src:
Uri Template:     url({protocol}://{host}{directory}{filename}_{scaleRounded}x.{ext})
Request Src:

Example C: Width and height in their own directory
Original Src:
Uri Template:     url({protocol}://{host}{directory}{requestWidth}x{requestHeight}/{file})
Request Src:

Example D: Width and height in the querystring
Original Src:
Uri Template:     url({protocol}://{host}{directory}{file}?w={requestWidth}&h={requestHeight})
Request Src:

Example E: Width in the filename, request to the same host
Original Src:     /images/myimage.jpg
Uri Template:     url({directory}{requestWidth}px-{file})
Request Src:      /images/320px-myimage.jpg

URI Find/Replace

The URI find/replace option keeps the original src URI in tact, but finds and replaces values within the URI with values foresight.js provides. For example, an image src many already contain a width values within the URI, and what foresight.js does is find the original browser width and replace it with the request width. The find/replace contains two values separated by the pipe (|) character.

URI Find/Replace Examples

Example A: Find the value 320px within the URL replace it with 640px
Original Src:       /images/320px-foo.jpg
Uri Find/Replace:   url(320px|640px)
Request Src:        /images/640px-foo.jpg

Example B: Find the term low-res and replace it with hi-res
Original Src:       /images/foo-low-res.jpg
Uri Find/Replace:   url(-low-res|-hi-res)
Request Src:        /images/foo-hi-res.jpg

Example C: Find the image's browser width and replace it with the request width
In this example the image's browser width is 320.
Original Src:       /images/320px-foo.jpg
Uri Find/Replace:   url({browserWidth}px|{requestWidth}px)
Request Src:        /images/640px-foo.jpg

Example D: Find the image's browser width/height and replace it with the request width/height
Original Src:       /images/320x240/foo.jpg
Uri Find/Replace:   url({browserWidth}x{browserHeight}|{requestWidth}x{requestHeight})
Request Src:        /images/640x480/foo.jpg

image-set() Examples

The image-set() provides a list of variants which foresight.js can choose from to apply to an image. How foresight.js decides which image-set variant to use is up to the device's pixel ratio and bandwidth. Below are a few examples of how image-sets would be applied according to the device.

Example A Image-Set:

Example image-set has one find/replace variant, which is only for 2x and high-bandwidth devices:
image-set( url(_px{browserWidth}|_px{requestWidth}) 2x high-bandwidth )

Test 1 for Example A:
Device Pixel Ratio: 1
Bandwidth: low
End-state: Since this device is neither 2x or high-bandwidth then the single image-set variant 
           does not apply. Since none apply, foresight.js will use the original src.

Test 2 for Example A:
Device Pixel Ratio: 2
Bandwidth: low
End-state: This device does have 2x pixel ratio, but does not have or high-bandwidth.
           Since bandwidth does not apply, foresight.js will use the original src.

Test 3 for Example A:
Device Pixel Ratio: 2
Bandwidth: high
End-state: This device has both a 2x pixel ratio and high-bandwidth.
           Since both apply, foresight.js will use the find/replace image-set variant.

Test 4 for Example A:
Device Pixel Ratio: 1.5
Bandwidth: high
End-state: This device has a device pixel ratio of 1.5, which rounds up to a 2. This 
           device also has a high-bandwidth. Since both apply, foresight.js will use 
           the find/replace image-set variant.

Example B Image-Set:

Example image-set has two URI templates:
image-set( url({directory}{filename}-low-res.{ext}), url({directory}{filename}-high-res.{ext}) 2x )

Test 1 for Example B:
Device Pixel Ratio: 1
Bandwidth: low
End-state: Since this device is not 2x then it will not apply the second image-set item, which
           is the hi-res version. Notice that the second image-set variant actually doesn't care
           about bandwidth. Since the first image-set variant will be applied the image will add
           "-low-res" to the end of the image filename.

Test 2 for Example B:
Device Pixel Ratio: 2
Bandwidth: low
End-state: This device has a 2x pixel ratio, but since the second image-set variant doesn't
           care about bandwidth then the hi-res image-set variant will be applied. The 
           resulting request source adds "-hi-res" at the end of the image filename.

Example C Image-Set:

Example image-set has three variants (on separate lines just so its easier to read, but sadly separate lines not allowed):
            url(/images/medium/{file}) 1.5x, 
            url(/images/large/{file}) 2x high-bandwidth

Test 1 for Example C:
Device Pixel Ratio: 1
Bandwidth: low
End-state: Since this device is not 1.5x or 2x then it will not apply the second or third image-set variant.
           Because the second and third do not apply, then the default variant, which is the first one,
           will be applied, resulting in requesting the file from the /images/small/ directory.

Test 2 for Example C:
Device Pixel Ratio: 2
Bandwidth: low
End-state: This device has a 2x pixel ratio, but it has a low-bandwidth, so the third variant does not apply.
           However, second image-set variant does apply because the device pixel ratio is greater than 1.5x
           and the second variant does not care which type of bandwidth the device has. The resulting
           request would be a file in the /images/medium/ directory.

Foresight.js Options

Foresight.js comes with default settings, but using foresight.options allows you to customize them as needed. The easiest way to configure foresight.js is to include the foresight.options configuration before the foresight.js script, such as:

    foresight = {
        options: {
            minKbpsForHighBandwidth: 500,
            speedTestExpireMinutes: 60
<script src="foresight.js"></script>

foresight.options.testConn: Boolean value determining if foresight.js should test the network connection speed or not. Default is true

foresight.options.minKbpsForHighBandwidth: Foresight.js considers a network connection to be either high-speed or not. When a device has a high-speed connection and hi-res display it will request hi-res images to be downloaded. However, everyone's interpretation of what is considered high-speed should be a variable. By default, any connection that can download an image at a minimum of 400Kbps is considered high-speed. The value should be a number representing Kbps. Default value is 300

foresight.options.speedTestUri: You can determine the URI for the speed test image. By default it will use a foresight.js hosted image, but you can always choose your own URI for the test image. Default value is (also note that if the webpage is in SSL, foresight.js will replace 'http:' for 'https:' to avoid any ugly security warnings)

foresight.options.speedTestKB: Foresight.js needs to know the filesize of the speed test file is so it can calculate the approximate network connection speed. By default it downloads a 50KB file. The value should be a number representing KiloBytes. Default value is 50

foresight.options.speedTestExpireMinutes: Speed-tests do not need to be continually performed on every page. Instead you can set how often a speed test should be completed, and in between tests you can rely on past test information. The value should be a number representing how many minutes a speed test is valid until it expires. Default value is 30

foresight.options.forcedPixelRatio: You can override the device pixel ratio value. This is used more so for debugging purposes. Default value is undefined

foresight.options.forcedBandwidth: You can override what the network bandwidth is with either low or high values. This is used more so for debugging purposes. Default value is undefined

Img Attributes

data-src: (Required) The src attribute of the image, which is the location image on the server. Note that the img element should not set the src attribute, but instead it sets a data-src attribute.

data-width: (Required) The pixel width according to the browser. Any adjustments to the device pixel ratio will take care of the request image width automatically. Both data-width and data-height are required so we can always proportionally scale the image.

data-height: (Required) The pixel height according to the browser. Any adjustments to the device pixel ratio will take care of the request image height automatically. Both data-width and data-height are required so we can always proportionally scale the image.

data-high-resolution-src: (Optional) Alternatively to dynamically building the img's src, you can manually set the data-high-resolution-src attribute which is used when the device is high-resolution enabled. Any device pixel ratio greater than 1 is considered high-resolution. For example, devices with a pixel ratio of 1.5 and 2 will both receive the same image.

Foresight.js Properties

After foresight.js executes there are a handful of properties viewable.

foresight.images: An array containing each of the foresight.js img elements.

foresight.devicePixelRatio: The device's pixel ratio used by foresight. If the browser does not know the pixel ratio, which older browsers will not, the devicePixelRatio defaults to 1.

foresight.connType: The connection type used by the device, such as 2g, 3g, 4g, eternet, wifi, etc. Currently only some Android devices seem to support navigator.connection.type. But for the devices that do support this, and they state that they are using either a 2g or 3g connection, foresight.js doesn't even bother doing a speed test. See W3C Network Information API for more info.

foresight.connTestResult: The connection test result provides info on how the device received its speed-test information. Below are the possible values:

  • networkSuccess: The speed test information came directly from a network test.
  • networkSlow: A 50KB file should be downloaded within 1 second on a 400Kbps connection. If the speed test takes longer than 1 second than we already know its not a high-speed connection. Instead of waiting for the response, just continue and set that this network connection is not a high-speed connection.
  • networkError: When a speed-test network error occurs, such as a 404 response, the connTestMethod will equal networkError and will not be considered a high-speed connection.
  • networkAbort: When a speed-test network abort occurs, the connTestMethod will equal networkAbort and will not be considered a high-speed connection.
  • connTypeSlow: The device stated that it is using either a 2g or 3g connection, which in this case we do not perform a speed test and just consider this device to not have a high-speed connection.
  • localStorage: A speed-test does not need to be executed on every webpage. The browser's localStorage function is used to remember the last speed test information. When the last speed-test falls outside of the foresight.options.speedTestExpireMinutes option it execute a new speed-test again.
  • skip: If the device pixel ratio equals 1 then the display cannot view hi-res images. Since high-resolution doesn't apply to this device, foresight.js doesn't bother testing the network connection.

foresight.connKbps: Number representing the estimated Kbps following a network connection speed-test. This value can also come from localStorage if the last test was within the foresight.options.speedTestExpireMinutes option. Note that foresight.connKbps is not an extremely accurate assessment of the device's connection speed, but rather provides a fast look to see if it can download a file quickly (and then remembers that test info for a configurable number of minutes).

foresight.bandwidth: String value which is either low or high and used to tell foresight.js if this device's bandwidth is low-bandwidth or high-bandwidth. You can use the foresight.options.minKbpsForHighBandwidth configuration option to help determine what is considered high-bandwidth. See the minKbpsForHighBandwidth config description for more info.

Foresight.js Methods

foresight.reload: Call this method when your code changes the DOM. However, foresight.reload is automatically executed on any window resize event. Take a look at the jQuery Mobile integration and the demos on an example of how it would be used.

jQuery Mobile Integration

Foresight.js does not require the jQuery library or jQuery Mobile framework, but it can still be easily integrated into jQuery Mobile. Below is a sample of what the head element would contain so foresight.js can be used:

<script src=""></script>
<script src=""></script>
<script src="foresight.js"></script>
    $(document).bind("pagechange", foresight.reload);

Notice how it binds the foresight.reload method when a page change happens, this ensures all new images to the DOM are correctly loaded by foresight. Take a look at the jQuery Mobile demo pages to see it in action.

Foresight.js Events

foresight.updateComplete: Executed after foresight.js rebuilds each of the image src's.

Foresight.js Debugging

Instead of including debugging code directly in the foresight.js, an additional javascript file has been included to help developers debug. By using the foresight.updateComplete event and populated foresight properties, the foresight-debug.js file prints out relevant information to help debug. This is particularly useful for mobile devices since it is more difficult to view source code and javascript errors. Below is an example on how to include the foresight-debugger.js file and calling it when foresight.js completes:

    foresight = {
        options: {
            minKbpsForHighBandwidth: 800,
            speedTestExpireMinutes: 60
<script src="foresight-debugger.js"></script>
<script src="foresight.js"></script>


Foresight's goal has always been to work on the major browsers, both desktop and mobile, and not require any javascript libraries or frameworks. If you come across any problems please help us by submitting an issue and we'll work to improve it. Below are the primary browsers foresight.js has been tested against.

  • iOS 5.1 (iPad3 & iPhone4)
  • Android 2.3 (Samsung Charge)
  • Chrome 17 (Mac)
  • Chrome 19 (Win)
  • Safari 5.1 (Mac)
  • Firefox 11 (Mac)
  • Firefox 10 (Win)
  • IE8


This project was originally created as a need for an ecommerce mobile homepage, which basically showed high-resolution images for high-resolution devices, and adjust image widths accordingly. This is by no means the end-all solution for high-resolution images; I'd label this more as an interim solution as the web standards evolve for handling device pixel ratios. Please feel free to improve this project in any way you can.

Contact Me

Bug tracker

Find a bug? Please create an issue here on GitHub!

Submit an issue



Copyright (c) 2012 Adam Bradley

Licensed under the MIT license.

Something went wrong with that request. Please try again.