Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
A browsable, searchable and easily customizable archive and backup for your tweets
branch: master

Merge pull request #65 from oelna/master

Implemented the preg_replace_callback() changes done in #63 in a PHP <5.3 compatible way
latest commit 984feffeb1
@graulund authored
Failed to load latest commit information.
archive Added folder for json archive files exportet from twitter
extensions Update images.php
inc tried to implement preg_replace_callback() in a way that doesn't make…
maintenance Last minute tweaks and herp derp fixes
styles/streamlined Tweet Nest 0.8 launch
.gitignore Better foundations.
.gitmodules Better foundations.
LICENSE.txt Tweet Nest 0.8 launch Updating readme
authorize.php Including upgrade.php within authorize.php for uber convenience
callback.php Last minute tweaks and herp derp fixes
day.php Tweet Nest 0.8 launch
favorites.php Tweet Nest 0.8 launch
index.php Tweet Nest 0.8 launch
month.php Tweet Nest 0.8 launch
redirect.php Better foundations.
search.php Tweet Nest 0.8 launch
setup.php Tiny note change in setup
sort.php Tweet Nest 0.8 launch
tweets.js Removing deprecated @Anywhere support, and upping jQuery version
upgrade.php Expanding tweet text column size for database software that supports it

This is Tweet Nest

Tweet Nest is a browsable, searchable and easily customizable archive and backup for your tweets, made in PHP. It runs on a web server.

It requires the following:

  • PHP 5.2 or higher with cURL enabled (or 5.1 with the PECL JSON module installed in addition)
  • MySQL 4.1 or higher

To figure out how to install it, please point your browser to:

And go to the "Installation" section.


Andy Graulund

Twitter archive import

  • Place your downloaded json archive files (data/js/tweets/[year]_[month].js) directly in the archive folder (archive/[year]_[month].js)
  • On new tweet nest setups:
  • On existing instances:
    • be sure not to overwrite your inc/config.php or you will have to setup your instance again
    • run upgrade.php
    • run maintenance/loadarchive.php

The importer keeps track of its progress in maintenance/loadarchivelog.txt if it's writable. Should the script die for some reason (php time limit e.g.), just run it again.

If you have a large archive (10k+ tweets), I would recommend to do the one-time import via cli (php -f maintenance/loadarchive.php)

Something went wrong with that request. Please try again.