Since version 1.0, UpShot supports using your own custom domain name to share your screenshots via Dropbox.

However, you have to do some work on the server side to make it happen. Here are two ways to point your own, custom domain at your public Dropbox folder.

Option 1: Server Config (or .htaccess)

If you have your own server or webhosting set up, you can redirect a domain or directory to Dropbox, like this:

where XYZ is your Dropbox user ID number.

This is how:

  1. First, set up a (sub-)domain with your web hosting company (e.g., The process varies depending on your hosting company. Hook up that domain to a directory on your web server.
  2. Alternatively, just create a subdirectory on a domain you own, such as:


Either edit the server config for the new domain or create a new file .htaccess in the directory that your domain is connected to, containing:

RewriteEngine on
RewriteRule ^(.*)$$1 [L,QSA]

Change XYZ to your Dropbox ID number. You can find that number in your UpShot Preferences window.

With this setting, your screenshot URLs will look like this:

These URLs will work for all files in your Public directory. If you want to use this domain only for screenshots uploaded by UpShot, you can add the Screenshots/ directory in there as well:

RewriteRule ^(.*)$$1 [L,QSA]

This further shortens the URLs to!


This same solution works with any other web browser that supports regex-driven redirects as well, like lighttpd (which is what I use).

Here's a little config snippet from my lighttpd.conf file:

$HTTP["host"] =~ "^i\.example\.com" {
  url.redirect = (
    "^/(.*)$" => "$1",
  url.redirect-code = 302

This will have the same effect as the Apache code above: redirecting my personal domain to my public Dropbox.

Option 2: CNAME

There's another option that doesn't require any changes to your server. However, you'll need access to your provider's DNS settings.

If you do have such access, you can create a DNS CNAME record. A CNAME record is essentially a domain alias, forwarding one domain name to another.

It's pretty simple:

  1. Access your provider's DNS settings menu. Providers should have a help file about how to do this, like this one from Hover.
  2. Add a new DNS record, type: CNAME.
  3. Choose a domain name (such as and point it to

Once the changes have been picked up by the DNS system, you're done! Your screenshots will be available under a URL like:

While certainly elegant, one (big) caveat of this solution is that the resulting URLs still contain the portion /u/XYZ/Screenshots. Because the CNAME record works purely on a domain level, there is no way for us to hide this portion of the URLs with this method.

Additional methods

(Updated 12/10/2012)

Here are some additional solutions to this problem that I haven't covered here because they were a little too complicated or inefficient for my taste. But still, they are certainly options for you to consider.

  • You can use Google App Engine (or really any other script-enabled server) to proxy your domain to Dropbox. When a URL is called, the script will actually download that file from your dropbox, then serve it to you from GAE (introducing the obvious double bandwidth and latency, but completely hiding the fact that it is powered by Dropbox in the backend).
  • You can also install a text-only instance of Dropbox on your server. It would then behave like any other of your devices (syncing from Dropbox automatically) and you could simply serve up the desired folder(s) as static files via a regular web server. (Getting this set up seems quite complicated, but once done, you wouldn't even need a Public folder any longer). (Thanks to Jabba for the hint)

Now go ahead and set up your domains as aliases for your Dropbox accounts. Then you'll be able to use it with UpShot to share screenshots.

If you have any other solutions in mind, any questions or concerns, please leave a comment below!

Was this helpful? Buy me a coffee with Bitcoin! (What is this?)

Updating Adobe Flash Without Restarting Firefox

No reason for a Flash upgrade to shut down your entire browser, even if it claims so.It's 2015, and the love-hate relationship of the Web...… Continue reading

Reddit's Fail-Alien (or "Fail-ien?")

Published on January 15, 2015