Launch Google Chrome from the command line with specific window coordinates Launch Google Chrome from the command line with specific window coordinates google-chrome google-chrome

Launch Google Chrome from the command line with specific window coordinates


When you're using Google's Chrome, there is a shorter way:

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"      --profile-directory="Default"     --app="data:text/html,<html><body><script>window.moveTo(580,240);window.resizeTo(800,600);window.location='http://www.test.de';</script></body></html>"

Pro:

  • Automatically opens the window
  • Avoids the popup-blocker
  • Opens multiple windows on different monitors (multi monitor setup, requires two or more Chrome profiles)

Con:

  • Only seems to work in "app" Mode
  • Not tested with other browsers


http://peter.sh/experiments/chromium-command-line-switches/ says --window-position=x,y is what you're looking for.

Updating this years later to include a small shell script I wrote years ago (but after answering this question) that provides an example of how to start chrome with custom window sizes/position and has the ability to create 'fake' user data directories by name.

It may or may not still work, and has some dangerous options set, but you get the idea.. Do not use this verbatim, some of the flags may have been renamed or been removed entirely.. (like the socks proxy commands did)

#!/bin/bash -xFAKEUSER="${1:-fake-chrome-user}"CHROMEROOT=$HOME/.chromeroot/mkdir -p ${CHROMEROOT}export PROFILE="${CHROMEROOT}/${FAKEUSER}-chromium-profile"export DISK_CACHEDIR="${CHROMEROOT}/${FAKEUSER}-chromium-profile-cache"export DISK_CACHESIZE=4096export MEDIA_CACHESIZE=4096PARANOID_OPTIONS="\        --no-displaying-insecure-content \        --no-referrers \        --disable-zero-suggest \        --disable-sync  \        --cipher-suite-blacklist=0x0004,0x0005,0xc011,0xc007 \        --enable-sandbox-logging >/dev/null 2>&1        "/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \        --remember-cert-error-decisions \        --ignore-certificate-errors \        --ignore-urlfetcher-cert-requests \        --allow-running-insecure-content \        --window-position=2400,400 \        --window-size=1500,1000 \        --no-pings \        --user-data-dir=${PROFILE} \        --disk-cache-dir=${DISK_CACHEDIR} \        --disk-cache-size=${DISK_CACHESIZE} \        --media-cache-size=${MEDIA_CACHESIZE} \        2>&1#--proxy-server="socks4://localhost:30604" \#--host-resolver-rules="MAP * 0.0.0.0 , EXCLUDE localhost" \


To build on @synthesizerpatel's answer, --window-position won't work on it's own.

You'll need to launch it as it's own new instance using --user-data-dir or --chrome-frame like:

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"  --user-data-dir=XXXXXXXXXX --window-size=800,600 --window-position=580,240 --app="http://www.google.com/"or"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --chrome-frame --window-size=800,600 --window-position=580,240 --app="http://www.google.com/"

Unfortunately for me, having it as a new instance means it doesn't carry over the session/cookie/etc info from other instances, so I've had to open it normally (with only the --app parameter), then have javascript in the page I open do:

window.moveTo(580,240);window.resizeTo(800,600);

I guess if you were opening a webpage owned by someone else, you could open your own webpage that has the above js, and then navigates to their webpage.