Deploy to Netlify with pushd
Fast setup, reliable free hosting, clean URLs. Connecting it to pushd takes about two minutes.
What you need
- A free Netlify account
- A personal access token (created below)
Create the token
- In pushd, select Netlify and click Get token ↗ - it opens Netlify’s personal access tokens page.
- Click New access token, give it any name (e.g. “pushd”), select whichever expiry you want (if you lose the token or it expires you’ll need to create a new one) and create it.
- Copy the token.
Connect it
Paste the token into pushd’s token field. If successful, you’ll see a “Connected as” message, meaning you’re all set. If you see ✗, re-copy the token (easy to miss a character).
Your token is stored only in your browser’s local extension storage and sent only to Netlify’s API over HTTPS. pushd doesnt store or track it remotely.
Netlify’s personal tokens aren’t ‘scoped’, so treat it like a password - and you can revoke it any time from the same Netlify page.
Where your site lives
The site name you enter in the extension becomes the subdomain: a site named sourdough-recipes goes live at https://sourdough-recipes.netlify.app. Names are made URL-safe automatically (lowercase, hyphens, up to 63 characters). Netlify sites stay online permanently on the free plan.
Netlify subdomains are global, so if your site name was taken and already in-use, you’ll be assigned a random one from netlify instead.
Updating
Push again with the same site name you update the same site, usually live in seconds. pushd shows “Update site on Netlify” and “Same link as last time” so you know before you click. New name = new site.
Overwrite confirmation: if you already have a Netlify site that wasn’t created by pushd, pushd won’t touch it unless you tick “Overwrite if this name already exists” on the deploy screen. Deliberate deploys only.
Limits worth knowing
Netlify’s free plan runs on monthly credits worth roughly 15GB of traffic. A personal page won’t get near that - but if you hit the cap, sites pause until the month resets. Expecting real traffic? Cloudflare has no bandwidth cap.
Errors you might see
- “Token looks wrong - double-check it in your Netlify account.” The token is invalid or was revoked. Create a fresh one and reconnect.
- “Too many requests - wait a moment and try again.” Netlify rate limit - it passes in a minute.
- “Netlify could not process the upload.” Rare; usually a malformed file set. Try re-pushing, and check your files open locally.
More fixes: Troubleshooting.