Install

1. Install vips:
   1. Go to the latest vips release for Windows.
   2. Download the asset for your platform architecture with -all- in the name.
   3. Extract the archive, or at least the bin subfolder, to a path of your choosing.
   4. Add the full path of the extracted bin folder to your Path environment variable. (An easy way is to press the ⊞ Win key, type "env", and hit Enter, then proceed in the GUI.)
   5. Restart any open shells/command prompts, and enter echo %Path% to ensure the environment has been updated.
2. To process photos/videos from iPhones, install libheif by following their instructions.
3. Install ffmpeg:

   curl.exe https://webi.ms/ffmpeg | powershell

4. Install uv:

   powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

5. Download Timelinize (see above).
6. Extract the program, timelinize.exe.
7. Run the program (from the command line, for logs). We are not yet code-signed, so you will have to override built-in OS protections:
   • You will get a warning that this software is not signed. Click More info and then Run anyway.

1. Install libvips:

   brew install vips

2. To process photos/videos from iPhones, install libheif:

   brew install libheif

3. Install ffmpeg:

   brew install ffmpeg

   or

   curl https://webi.sh/ffmpeg | sh

4. Install uv:

   curl -LsSf https://astral.sh/uv/install.sh | sh

5. Download Timelinize (see above) and extract the archive to expose the binary.
6. We are not yet code-signed, so you will have to override the OS to run the app: follow these instructions to run apps from unidentified developers (that's me!).

Additional steps

Mac has a whole extra layer of kernel-level protections that go beyond posix-style file permissions, users, and groups, that will likely require additional steps:

7. If you get an error that says Timelinize "is damaged," that's a lie: the checksums probably match; the real problem is that Apple has placed it in "quarantine" because it was downloaded. You can either:
   • Do a two-finger ("right") click and select Open, twice (once for the warning, the second time to open it)
   • Or, open Terminal and run this command:

     xattr -d com.apple.quarantine ~/Downloads/timelinize

     (adjust path as needed).
8. If you get errors when opening or creating a timeline, when planning an import, or right after an import starts, Apple is likely blocking access to your files (especially if the error is something like "operation not permitted"). The easiest way around this is to give Terminal explicit access in Settings -> Privacy & Security. For access to everything, find "Full Disk Access" and add/enable Terminal: If you prefer, you can be more selective about what you grant access to by selecting more specific data instead, such as Photos, Contacts, or Files & Folders. Remember to grant it for Terminal, since Timelinize runs in the Terminal.

1. Install libvips:
   • Debian/Ubuntu/Raspbian:

     sudo apt install -y libvips

   • Arch:

     sudo pacman -S libvips

2. To process photos/videos from iPhones, install libheif:
   • Debian/Ubuntu/Raspbian:

     sudo add-apt-repository ppa:ubuntuhandbook1/libheif
     sudo apt update
     sudo apt install libheif1 libheif-plugin-libde265

   • Arch:

     sudo pacman -S libvips

3. Install ffmpeg:
   • Debian/Ubuntu/Raspbian:

     sudo apt install -y ffmpeg

   • Arch:

     sudo pacman -S ffmpeg

4. Install uv:

   curl -LsSf https://astral.sh/uv/install.sh | sh

5. Download Timelinize (see above).
6. Extract the program, and make sure it is executable: chmod +x ./timelinize
7. Run ./timelinize. A browser tab should open automatically.

Pull the automated Docker image from GHCR:

docker pull ghcr.io/timelinize/timelinize/

It can be run like so:

docker run -p12002:12002 \
	-v /path/to/repo:/repo \
	-v /path/to/config:/app/.config/timelinize \
	ghcr.io/timelinize/timelinize

That will run Timelinize on port 12002, with the timeline repository mounted at /path/to/repo (change it to suit your needs) and the configuration directory mounted at /path/to/config (change it). When using Docker bind mounts like above, make sure the directories exist on your host machine and that they belong to the user ID 1000.