Connect your Hostinger API token once. SiteShift lists your websites, pulls any of them down to a local copy on bundled PHP and MySQL, and pushes your changes back over Hostinger's SSH. No staging add-on, no File Manager uploads.
This site — site-shift.nl — is hosted on Hostinger and deployed with exactly this integration.
Hostinger's API can't hand out SSH hosts or passwords — those live in hPanel — so the integration does what the API can, and asks you for the one thing it can't.
Paste a Hostinger API token from hPanel. SiteShift reads your website list, so pulling a site is picking it from a dropdown instead of typing a hostname.
Starting a new project? Create the Hostinger website from inside SiteShift — pick the plan order and data centre — and it's ready to receive the first push.
Hostinger's SSH port (65002) and user (your hosting account name) are known, so SiteShift fills them in. The SSH host you paste once from hPanel → SSH Access, and SiteShift remembers it.
Websites → your site → Advanced → SSH Access. Note the host; the port is always 65002 and the user is your hosting account name.
hPanel → Account → API. Copy the token; SiteShift validates it before saving and stores it in its encrypted vault on your machine.
Hosting → Add account → Hostinger → paste the token. Your websites appear in the account's list.
New site → Pull from vendor → pick the website → paste the SSH host → Pull. Files and database arrive, URLs are rewritten to a local address, the site opens at its .localhost URL.
PHP 8.1–8.4 per site, one-click WP admin, and the files under ~/.siteshift/sites/
Review the file diff, optionally include the database (Hostinger's copy is backed up first), type the domain to confirm. Then purge LiteSpeed Cache in hPanel so visitors get the new version.
Learned by running this very site on it.
After a push, purge the cache (hPanel or the LiteSpeed plugin → Purge All), or the site looks unchanged until the cache expires.
SiteShift detects this and uses a writable path under your domain folder for its temporary archive and the database backup.
Set it per site in hPanel; pick the same one in SiteShift so what works locally works live.
Each Hostinger website lives under /home/
For most work, yes — you get unlimited local copies instead of one staging site per website. If a client needs to click through a preview, a Hostinger staging site is still the easiest place to push to; SiteShift can push there too, it's just another SSH connection.
SSH access is a plan feature on Hostinger's side — check Advanced → SSH Access in hPanel for your website. If the page is there and enabled, SiteShift can use it.
Tokens and SSH secrets live in SiteShift's encrypted vault on your machine (libsodium), never on our servers. SiteShift has no cloud component besides licence validation.
Yes, as a plain SSH connection. The API integration is for Hostinger's managed WordPress hosting; a VPS you link by pasting its SSH details.
Your Hostinger sites, one pull away.
Get SiteShift — €9/mo