Calculate page size and view port position in JavaScript


Have you ever had to try to figure out the dimensions of a page or browser in JavaScript? This task seems very simple at first glace, every browser has simple properties that will give you this information. Unfortunately, not every browser agrees what object these properties belong to, or even what the names are.

I’ve built a couple nifty tools in JavaScript that need to know the exact dimensions of the document as well as the exact dimensions of the browser view port. Since these scripts are uses on very high traffic sites with a very wide audience I have had to make sure they work in a multitude of browsers.

In this article I will show you how I support all modern (and not so modern) browsers with one function and I will explain a little about exactly what techniques I’m using to accomplish this.

When do you need to know page and view port dimensions?

Basically, whenever you are going to dynamically place absolute positioned elements on the document. I have built several JavaScript features that needed to know this information.

One good example is a Lightbox/Thickbox style image viewer. You need to place a box in the exact middle of the view port and have the ability to shrink it down to fit within the view port constraints.

An even better example was a pop up image thumbnail feature. When you put your mouse over certain links a thumbnail pops up to show you a picture or the logo of the link you’re about to click on. This image follows the mouse around, hanging just below and to the left of the cursor. Since I could never say for sure where the links will be on the page I have to know when the flip the image to the other side of the mouse to keep it from extending past the view port.

Dimensions needed for placement

View Port ExampleTo do any kind of dynamic absolute placement you need to know what your constraints will be. These bounds are generally going to be the browser view port, which is literally the browsers current view of your document, but it is a little more complex than that.

Think of the web browser as a window and the document as a paper underneath it. When you scroll down a page you are simply moving the document up in the view port. This means that if you want to position something based on the view port you will need to consider where the view port is on the page.

Horizontal bounds are simple (assuming you aren’t dealing with a very small browser), your constraints will be X=0 to X=View Port Width. Vertical bounds are a little more complicated. To compute vertical bounds on a page you have to factor in the current scrolled position of the view port in the document. So your vertical constraints will be Y=View Port Offset to Y=View Port Offset + View Port Height. Simple.

However those formulas are missing one critical piece that most browsers do not give you, scroll bar width. Most browsers consider the scroll bars to be inside of the view port so they are not factored in to the view port dimensions that the browsers will give you. If you create an element and push it in to a scroll bar it will increase the size of the document as the browser renders it, this leads to the “infinite scrolling phenomena”. Unfortunately the width of the scroll bars depends on the operating system.

It is basically impossible to compute the size of the scroll bars in such situations, so I picked an arbitrary number that seems to have appropriate padding on every systems that I’ve tested, 17 pixels.

Taking the 17 pixel padding into consideration our bounding formula now looks like this:

  • X = 0 to X = View Port Width – 17
  • Y = View Port Offset to Y = View Port Offset + View Port Width – 17

The browser properties

Basically every browser except Internet Explorer agrees where the dimensions information is located. Can’t say that I’m particularly surprised, Microsoft has made it their mission to complicate these things.

For a nice visual list of available properties and browser support check out the W3C DOM CSS Object Model Compatibility article on QuirksMode. It’s a very nice list of many useful properties and methods as well as a chart of what browsers support them and how effective their support is.

View port dimensions

I found three possible objects that contain the view port size information. In most browsers the self object has the properties of innerWidth and innerHeight. However Internet Explorer has two other objects, IE6 keeps this information in the document.documentElement object and all new IEs use the document.body object. These objects have a clientWidth and clientHeight property.

Document dimensions

Once again, I found three different ways to get the document measurements. Most browsers agree that this information is stored in the document.body object. However Firefox’s best measurement of total document height seems to be window.innerHeight + window.scrollMaxY. The rest of the browsers respond to the scrollWidth/scrollHeight or offsetWidth/offsetHeight.

Scroll offset

Last but not least is the scroll offset, and again three different possible locations for this information. The general consensus is that scroll offset can be found in the pageYOffset and pageXOffset properties of the self or window objects. However IE uses scrollTop and scrollLeft properties on the document.body or document.documentElement objects.

Short documents

One scenario that we need to be able to handle is that of a small document. If the document is smaller than the view port, such as a short page that doesn’t extend further down past the browser view, then we don’t want to use the document as our bounding constraints, we want to use the view port.

We do this by adding a simple test to see if if the view port height is greater than the document height and another test to see if the view port width is greater than the document width. In each case if it is greater then use the view port dimension instead of the document dimension.

The code

Here is the JavaScript code that I came up with. It is fairly short and simple and uses object detection, because you should always check for objects, never check for browsers.

This code is based on the work posted on QuirksMode some 6 years ago. The article has long since disappeared so I can’t give a better credit.

// Page Size and View Port Dimension Tools
if (!sb_windowTools) { var sb_windowTools = new Object(); };

sb_windowTools = {
	scrollBarPadding: 17, // padding to assume for scroll bars


	// center an element in the viewport
	centerElementOnScreen: function(element) {
		var pageDimensions = this.updateDimensions(); = ((this.pageDimensions.verticalOffset() + this.pageDimensions.windowHeight() / 2) - (this.scrollBarPadding + element.offsetHeight / 2)) + 'px'; = ((this.pageDimensions.windowWidth() / 2) - (this.scrollBarPadding + element.offsetWidth / 2)) + 'px'; = 'absolute';


	// load the page size, view port position and vertical scroll offset
	updateDimensions: function() {

	// load page size information
	updatePageSize: function() {
		// document dimensions
		var viewportWidth, viewportHeight;
		if (window.innerHeight && window.scrollMaxY) {
			viewportWidth = document.body.scrollWidth;
			viewportHeight = window.innerHeight + window.scrollMaxY;
		} else if (document.body.scrollHeight > document.body.offsetHeight) {
			// all but explorer mac
			viewportWidth = document.body.scrollWidth;
			viewportHeight = document.body.scrollHeight;
		} else {
			// explorer mac...would also work in explorer 6 strict, mozilla and safari
			viewportWidth = document.body.offsetWidth;
			viewportHeight = document.body.offsetHeight;
		this.pageSize = {
			viewportWidth: viewportWidth,
			viewportHeight: viewportHeight

	// load window size information
	updateWindowSize: function() {
		// view port dimensions
		var windowWidth, windowHeight;
		if (self.innerHeight) {
			// all except explorer
			windowWidth = self.innerWidth;
			windowHeight = self.innerHeight;
		} else if (document.documentElement && document.documentElement.clientHeight) {
			// explorer 6 strict mode
			windowWidth = document.documentElement.clientWidth;
			windowHeight = document.documentElement.clientHeight;
		} else if (document.body) {
			// other explorers
			windowWidth = document.body.clientWidth;
			windowHeight = document.body.clientHeight;
		this.windowSize = {
			windowWidth: windowWidth,
			windowHeight: windowHeight

	// load scroll offset information
	updateScrollOffset: function() {
		// viewport vertical scroll offset
		var horizontalOffset, verticalOffset;
		if (self.pageYOffset) {
			horizontalOffset = self.pageXOffset;
			verticalOffset = self.pageYOffset;
		} else if (document.documentElement && document.documentElement.scrollTop) {
			// Explorer 6 Strict
			horizontalOffset = document.documentElement.scrollLeft;
			verticalOffset = document.documentElement.scrollTop;
		} else if (document.body) {
			// all other Explorers
			horizontalOffset = document.body.scrollLeft;
			verticalOffset = document.body.scrollTop;
		this.scrollOffset = {
			horizontalOffset: horizontalOffset,
			verticalOffset: verticalOffset


	// raw data containers
	pageSize: {},
	windowSize: {},
	scrollOffset: {},

	// combined dimensions object with bounding logic
	pageDimensions: {
		pageWidth: function() {
			return sb_windowTools.pageSize.viewportWidth > sb_windowTools.windowSize.windowWidth ?
				sb_windowTools.pageSize.viewportWidth :
		pageHeight: function() {
			return sb_windowTools.pageSize.viewportHeight > sb_windowTools.windowSize.windowHeight ?
				sb_windowTools.pageSize.viewportHeight :
		windowWidth: function() {
			return sb_windowTools.windowSize.windowWidth;
		windowHeight: function() {
			return sb_windowTools.windowSize.windowHeight;
		horizontalOffset: function() {
			return sb_windowTools.scrollOffset.horizontalOffset;
		verticalOffset: function() {
			return sb_windowTools.scrollOffset.verticalOffset;

As you can see this object has several functions that go through all of our object checks and dimension calculations then provides an object with 5 simple properties that have every dimension we need for any kind of absolute placement.

Perhaps this code is more complex that is actually necessary, but I like to make my scripts very portable. I can drop this in anywhere and be able to get exactly what I need out of it.

Using the code

I have created a simple centerElementOnScreen function to demonstrate how all this works.

  • The first the you need to do before using any of the dimensions data is to get that data (or update it). You can load all of the dimensions data at once by calling the updateDimensions method.
  • Once you have called that method all of the information is loaded and made available through the pageDimensions methods. You call these methods directly to retrieve the information. So if you want to know how far the viewer has scrolled down the page you call sb_windowTools.pageDimensions.verticalOffset(). I know it’s kind of long, but I like descriptive names. Do not forget the parentheses, since I need to perform some logic on the pageHeight and pageWidth properties I had to make all of them functions.

Here is an example that will center a test element on the screen when the window loads:

window.onload = function() {
	// center the test element on the screen

Handling browser scrolling and resizing

Ideally, you will only need to compute these dimensions once, when you build whatever element you are trying to build. However you may need to handle the browser scrolling or resizing after you have done whatever work you needed to do.

The simplest solution is to call the function again and update your interface whenever the window.onscroll or window.onresize events are fired. I’ve tried to make this function as efficient as possible for a stand-alone function but it will have to recalculate information that surely hasn’t changed. Of course there is a more efficient way, but it requires some additional code.

What we can do is add just the needed code to the window events. Here is an example that will update just the scroll offset and reposition the element whenever the user scrolls the page.

window.onscroll = function() {
	// update the scroll information
	// update the vertical position of the element
	var element = document.getElementById('test'); = ((sb_windowTools.pageDimensions.verticalOffset() + sb_windowTools.pageDimensions.windowHeight() / 2) - (sb_windowTools.scrollBarPadding + element.offsetHeight / 2)) + 'px';

Now, when the user scrolls it will only update the needed information. This is really unnecessary, simply calling the centerElementOnScreen method in the onscroll event is perfectly acceptable. The execution time is so minimal that you really shouldn’t even bother. But if you are incredibly obsessive about optimizing your JavaScript code then this is the way to do it.

Working example

Here is a working example with this code.

Click “Center Me!” and scroll. Click “Cancel” to reset.

Please note that this is not the best way to keep an element in a fixed position on the page. It’s just a good example of the code.


There, I’ve successfully made a simple task complex and difficult to understand. I hope at least some of this information will be useful to someone out there! If you have any questions or comments please leave them in the form below and I will respond asap.

Updated: Apr 25th, 2010


  1. BenjoTLV

    Hi, very interesting and complete example, thanks a lot, really!

    I have few questions if you don’t mind:
    I am using in a desktop application a light version of Google Chrome (chromium actually) that is based on webkit. The browser window size I incorporated in my app is pretty small and I need to achieve several things:

    1. detect the document height and width in order to give it to my app and handle the vertical scollbar outside of the browser – I think I can achieve that with the code you provided, right?
    2. I need to force the document to have the width of my browser window to avoid horizontal scrollbars… do you see a way to force content/document to fit the width once I get the value through your technique?

    Thanks a lot again!

  2. You could use this code to set a wrapper div to the exact width and height of the browser view port, but that isn’t what I would recommend.

    The best way to support small screens is elastic design using nothing but CSS. There are many good tutorials out there on elastic design, but the technique is basically to use percentage and em measurements for the layout instead of pixels.

    If you really do need to be able to update some styles via JavaScript to fit the screen you can use the code from this article. Here’s an example:

    Let’s say that you want to adjust the width on a wrapper div, here’s what your document may look like:

    <div id="wrapper">
    	<!-- your content here -->

    Then this script will target the markup above and fit it to the screen:

    function fitWrapperToScreen() {
    	var div = document.getElementById('wrapper'); = sb_windowTools.pageDimensions.windowWidth() + 'px'; = sb_windowTools.pageDimensions.windowHeight() + 'px';

    Again, this should be done with elastic techniques. You could skip all of this and get a better effect with the following CSS:

    #wrapper {
    	width: 100%;
    	height: 100%;

    If you needed to support other browsers there would probably be some extra issues, but I believe these should work fine in WebKit. If you are having a problem with your content pushing out the div just add overflow: hidden; or overflow: scroll;.

  3. Shelby Moore

    I think your pageSize() is incorrect in some scenarios, because it is relying on window.innerWidth/Height, which will include the size of any visible scroll bars. As long as the DOCTYPE is declared Transistional, then ScrollWidth/Height is sufficient:

    Also it is incorrect to say that we can not detect the scrollbar sizes in all browsers other than IE, as this is window.innerwidth/Height – document.(body or documentElement).clientWidth/Height. Also we can detect the scroll bar sizes in IE also, but I will leave this for you to figure out.

  4. Shelby Moore

    The viewport size function on this page is wrong. Here is the corrected way to get the viewport consistently, and sans any visible scrollbar(s):

  5. James

    Thanks for taking the time to prepare that, just what I needed. And saved in my bookmarks for future reference. James

  6. This article JUST SAVED MY LIFE. Period. I implemented it to show a permanent, vertically-moving ads carousel and a main navigation bar for pages that are deeper than the browser window. Awesome and a million thanks!

  7. Ade


    Excellent article! Very handy code… Thanks so much, sure it’ll help me out with my task ;)

  8. Mike M


    Many thanks for your hard work.

    I used your code in my “Indy Web Journal” which displays various quantities of thumbnail images. When the user clicks a thumbnail, I wanted the larger version of the image to pop up in the horizontal and vertical center of the viewport. It works perfectly!!! I embedded your code in my own JavaScript and credited you in various places in the code. Thanks again! – Mike M.

Leave a reply