Features Videos Help About Updates
Menu Buy Now

Troubleshooting

First Steps:
Getting Started
Live-Reload Browsers
Browser Sync
Set Language Options
Set Output Paths & Action
Second Steps:
Defaults For New Projects
Build Your Project
Set Target Browsers
Stuff To Know:
CodeKit + Git
Troubleshooting
License Recovery
PostCSS Tools:
Autoprefixer
PurgeCSS
Custom PostCSS Plugins
Other Tools:
npm
Babel — (JS Transpiler)
Terser — (JS Minifier)
Rollup — (JS Bundler)
Cache-Buster
HTML-Minifier
LightningCSS
Bless
Languages:
Sass
Less
Stylus
JavaScript
CoffeeScript
TypeScript
Pug
Haml
Slim
Kit
Markdown
JSON
Image Optimizers:
WebP
PNG
JPEG
SVG
GIF
Frameworks:
CodeKit Frameworks
Tailwind
Bootstrap
Bourbon
Bitters
Zurb Foundation
Susy
Nib
Jeet
Syntax Checkers:
ESLint
Advanced:
Hooks
Environment Variables
Adding Custom Languages
Team Workflows
Scripting CodeKit
Editor Plugins:
Nova
Atom
Sublime Text
Coda 2
More
Read-Only Mode
Upgrading From 2.0
FAQ

Browsers Are Not Refreshing

First, make sure you've read the Browser Refreshing section or watched the screencast. If you still have a problem:

1. Try another preview address

Open the Server Popover in CodeKit by clicking the button in the top right. There are three Preview addresses listed. If the Bonjour one is not working, try the Non-Bonjour one.

2. Check your output paths

Browser refreshing may be working fine, you just don't see any changes because your file is not compiling to the spot you think it is. Make sure your Sass file is creating the CSS file that your page includes, for example.

3. Be sure the browser is visible

To save power, macOS won't redraw content in a browser if its window is not visible.

4. Turn off Internet Sharing

Open System Preferences > Sharing and disable Internet Sharing. This service blocks the Bonjour name resolution that makes CodeKit's server work.

5. Disable browser plugins

Some plugins, such as Adobe Edge Inspect, are not compatible with CodeKit. Disable all plugins or try a browser without them installed to verify that they aren't the issue.

6. Disable other JavaScript

Temporarily disable scripts on your page to see if one is conflicting with CodeKit. (Prefix-Free is a known example. Use AutoPrefixer in CodeKit instead.)

7. Verify the content-type

CodeKit will only refresh pages that use the text/html content-type. Inspect your HTTP response headers in the browser's console. If you're viewing a document with text/plain or another content-type, CodeKit can't refresh that.

8. Make sure your LAN is not using "Client Isolation"

For security, some networks (such as public WiFi) enable "Client Isolation", which prevents one device on the network from talking to another. Unfortunately, this means that CodeKit cannot refresh separate devices on that network. Browsers on your Mac will still refresh, however.

9. Be sure the text encoding is UTF-8

If your page uses an encoding other than UTF-8, CodeKit may not parse the contents correctly. It's 2017; there's no reason to use anything but UTF-8 at this point.

10. Be sure your OS is supported

On Apple devices, you must be on iOS 6+. On Android, you must be on 4.3+. On Windows, you must be on IE 10+. Older browsers do not support HTML5 websockets, which is how CodeKit communicates with the page.

Made in San Diego, CA

Follow the Developer on Twitter

Email Support

Report a Bug

Privacy Policy