You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
NAme 4519c076b8
2 years ago
docker [FEATURE] Add docker image support 4 years ago
lib Merge in v3.4.0 3 years ago
media tiny style fix of the upload_image_email 4 years ago
.gitignore [FEATURE] Ignore "custom" theme folder 4 years ago
.gitlab-ci.yml [FEATURE] Add Gitlab CI 4 years ago [TASK] complete 4 years ago
Dockerfile [FEATURE] Add docker image support 4 years ago
LICENSE.txt [TASK] Rename license file 4 years ago Update 2 years ago
admin.php [TASK] set a translation string id for each element 3 years ago
f.php [TASK] set a translation string id for each element 3 years ago
index.php [BUGFIX] move browser error to separate lang item 3 years ago
install.php [TASK] Remove lang selection in installation step 3 years ago
script.php Updated script.php to also output view link 3 years ago
tos.php [TASK] Remove useless title in TOS 3 years ago


This repo exists purely to maintain this commit, which allows previewing of files uploaded via API 762a73c409 You can try a hosted version of this repo at

Welcome to the official Jirafeau project, an Open-Source software.

Jirafeau allows your to "one-click-filesharing". It makes possible to upload a file in a simple way and give an unique link to it.

A demonstration of the latest version is available on


Latest CI Status: Master Build Status Master Next Release Build Status Next Release All Branch Builds

Main features

  • One upload → One download link & one delete link
  • Send any large files (thanks to the HTML5 file API → PHP post_max_size limit not relevant)
  • Shows progression: speed, percentage and remaining upload time
  • Preview content in browser (if possible)
  • Optional password protection (for uploading or downloading)
  • Set expiration time for downloads
  • Option to self-destruct after first download
  • Shortened URLs using base 64 encoding
  • Maximal upload size configurable
  • NO database, only use basic PHP
  • Simple language support 🇬🇧 🇫🇷 🇩🇪 🇮🇹 :nl: :ro: :sk: :hu: :cn: :gr: :ru: :es: :tk: :flag_tr: :flag_pt: :flag_br:
  • File level Deduplication for storage optimization (does store duplicate files only once, but generate multiple links)
  • Optional data encryption
  • Small administration interface
  • CLI script to remove expired files automatically with a cronjob
  • Basic, adaptable »Terms Of Service« page
  • Basic API
  • Bash script to upload files via command line
  • Themes

Jirafeau is a fork of the original project Jyraphe based on the 0.5 (stable version) with a lot of modifications.

As it's original project, Jirafeau is made in the KISS way (Keep It Simple, Stupid).

Jirafeau project won't evolve to a file manager and will focus to keep a very few dependencies.



This shows how to install Jirafeau by your own, it's quite simple but you can also use a docker image or build it yourself. Check docker folder for more informations.

System requirements:

  • PHP >= 5.6
  • Optional, but recommended: Git >= 2.7
  • No database required, no mail required

Installation steps:

  • Clone the repository or download the latest (release from GitLab onto your webserver
  • Set owner & group according to your webserver
  • A) Setup with the installation wizard (web):
    • Open your browser and go to your installed location, eg.
    • The script will redirect to you to a minimal installation wizard to set up all required options
    • All optional parameters may be set in lib/config.local.php, take a look at lib/config.original.php to see all default values
  • B) Setup without the installation wizard (cli):
    • Just copy config.original.php to config.local.php and customize it


General procedure for all versions

  1. Backup your Jirafeau installation!
  2. Block access to Jirafeau
  3. Checkout the new version with Git using the tagged release
    • If you have installed Jirafeau just by uploading files on your server, you can download the desired version, overwrite/remove all files and chown/chmod files if needed. Keep a backup of your local configuration file tough.
  4. With you browser, go to your Jirafeau root page
  5. Follow the installation wizard, it should propose you the same data folder or even update automatically
  6. Check your /lib/config.local.php and compare it with the /lib/config.original.php to see if new configuration items are available

From version 1.0 to 1.1

  1. The download URL changed
    • Add a rewrite rule in your web server configuration to rename file.php to f.php to make older, still existing links work again
  2. The default theme changed
    • Optionally change the theme in lib/config.local.php to »courgette«

From version 1.2.0 to 2.0.0

  1. The "Terms of Service" text file changed
    • To reuse previous changes to the ToS, move the old /tos_text.php file to /lib/tos.local.txt and remove all HTML und PHP Tags, leaving a regular text file

from version 2.0.0 to 3.3.0

There is nothing special to do to update from/to the following versions:

  • 2.0.0 -> 3.0.0
  • 3.0.0 -> 3.1.0
  • 3.1.0 -> 3.2.0
  • 3.2.0 -> 3.2.1
  • 3.2.1 -> 3.3.0


If you have some troubles, consider the following cases

  • Check your /lib/config.local.php file and compare it with /lib/config.original.php, the configuration syntax or a parameter may have changed
  • Check owner & permissions of your files


var directory contain all files and links. It is randomly named to limit access but you may add better protection to prevent un-authorized access to it. You have several options:

  • Configure a .htaccess
  • Move var folder to a place on your server which can't be directly accessed
  • Disable automatic listing on your web server config or place a index.html in var's sub-directory (this is a limited solution)

If you are using Apache, you can add the following line to your configuration to prevent people to access to your var folder:

RedirectMatch 301 ^/var-.* http://my.service.jirafeau

If you are using nginx, you can add the following to your $vhost.conf:

location ~ /var-.* {
    deny all;
    return 404;

If you are using lighttpd, you can deny access to var folder in your configuration:

$HTTP["url"] =~ "^/var-*" {
         url.access-deny = ("")

You should also remove un-necessessary write access once the installation is done (ex: configuration file). An other obvious basic security is to let access users to the site by HTTPS (make sure web_root in you config.local.php is set with https).

Server side encryption

Data encryption can be activated in options. This feature makes the server encrypt data and send the decryt key to the user (inside download URL). The decrypt key is not stored on the server so if you loose an url, you won't be able to retrieve file content. In case of security troubles on the server, attacker won't be able to access files.

By activating this feature, you have to be aware of few things:

  • Data encryption has a cost (cpu) and it takes more time for downloads to complete once file sent.
  • During the download, the server will decrypt on the fly (and use resource).
  • This feature needs to have the mcrypt php module.
  • File de-duplication will stop to work (as we can't compare two encrypted files).
  • Be sure your server do not log client's requests.
  • Don't forget to enable https.

In a next step, encryption will be made by the client (in javascript), see issue #10.


GNU Affero General Public License v3 (AGPL-3.0).

The GNU Affero General Public License can be found at

Please note: If you decide do make adaptions to the source code and run a service with these changes incorporated, you are required to provide a link to the source code of your version in order to obey the AGPL-3.0 license. To do so please add a link to the source (eg. a public Git repository or a download link) to the Terms of Service page. Take a look at the FAQ to find out about how to change the ToS.

PS: If you have fixed errors or added features, then please contribute to the project and send a merge request with these changes.


If you want to contribute to project, then take a look at the git repository:

and the Contribution Guidelines


Can I add a new language in Jirafeau?

Of course ! Translations are easy to make and no technical knowledge is required.

Simply go to Jirafeau's Weblate.

If you want to add a new language in the list, feel free to contact us or leave a comment in ticket #9.

We would like to thank all anonymous contributors on weblate. :)

How do I upgrade my Jirafeau?

See upgrade instructions above.

How can I limit upload access?

There are two ways to limit upload access (but not download):

  • you can set one or more passwords in order to access the upload interface, or/and
  • you can configure a list of authorized IP (CIDR notation) which are allowed to access to the upload page

Check documentation of upload_password and upload_ip parameters in lib/config.original.php.

How can I automatize the cleaning of old (expired) files?

You can call the admin.php script from the command line (CLI) with the clean_expired or clean_async commands: sudo -u www-data php admin.php clean_expired.

Then the command can be placed in a cron file to automatize the process. For example:

# m h dom mon dow user  command
12 3    * * *   www-data  php /path/to/jirafeau/admin.php clean_expired
16 3    * * *   www-data  php /path/to/jirafeau/admin.php clean_async

I have some troubles with IE

If you have some strange behavior with IE, you may configure compatibility mode.

Anyway I would recommend you to use another web browser. :)

How can I change the theme?

You may change the default theme to any of the existing ones or a custom.

Open your lib/config.local.php and change setting in the »style« key to the name of any folder in the /media directory.

Hint: To create a custom theme just copy the »courgette« folder and name your theme »custom« (this way it will be ignored by git and not overwritten during updates). You are invited to enhance the existing themes and send pull requests however.

I found a bug, what should I do?

Feel free to open a bug in the GitLab's issues.

How to set maximum file size?

If your browser supports HTML5 file API, you can send files as big as you want.

For browsers who does not support HTML5 file API, the limitation come from PHP configuration. You have to set post_max_size and upload_max_filesize in your php configuration.

If you don't want to allow unlimited upload size, you can still setup a maximal file size in Jirafeau's setting (see maximal_upload_size in your configuration)

How can I edit an option?

Documentation of all default options are located in lib/config.original.php. If you want to change an option, just edit your lib/config.local.php.

How can I change the Terms of Service?

The license text on the "Terms of Service" page, which is shipped with the default installation, is based on the »Open Source Initiative Terms of Service«.

To change this text simply copy the file /lib/tos.original.txt, rename it to /lib/tos.local.txt and adapt it to your own needs.

If you update the installation, then only the tos.original.txt file may change eventually, not your tos.local.txt file.

How can I access the admin interface?

Just go to /admin.php.

How can I use the scripting interface (API)?

Simply go to /script.php with your web browser.

My downloads are incomplete or my uploads fails

Be sure your PHP installation is not using safe mode, it may cause timeouts.

If you're using nginx, you might need to increase client_max_body_size or remove the restriction altogether. In your nginx.conf:

http {
    # disable max upload size
    client_max_body_size 0;
    # add timeouts for very large uploads
    client_header_timeout 30m;
    client_body_timeout 30m;

How can I monitor the use of my Jirafeau instance?

You may use Munin and simple scripts to collect the number of files in the Jirafeau instance as well as the disk space occupied by all the files. You can consult this web page.

Why forking?

The original project seems not to be continued anymore and I prefer to add more features and increase security from a stable version.

What can we expect in the future?

Check issues to check open bugs and incoming new stuff. :)

What about this file deduplication thing?

Jirafeau uses a very simple file level deduplication for storage optimization.

This mean that if some people upload several times the same file, this will only store one time the file and increment a counter.

If someone use his/her delete link or an admin cleans expired links, this will decrement the counter corresponding to the file.

When the counter falls to zero, the file is destroyed.

As explained in the previous question, files with the same md5 hash are not duplicated and a reference counter stores the number of links pointing to a single file. So:

  • The button "delete link" will delete the reference to the file but might not destroy the file.
  • The button "delete file and links" will delete all references pointing to the file and will destroy the file.

How to contact someone from Jirafeau?

Feel free to create an issue if you found a bug.

Release notes

Version 1.0

The very first version of Jirafeau after the fork of Jyraphe.

  • Security fix
  • Keep uploader's ip
  • Delete link for each upload
  • No more clear text password storage
  • Simple langage support
  • Add an admin interface
  • New Design
  • Add term of use
  • New path system to manage large number of files
  • New option to show a page at download time
  • Add option to activate or not preview mode

Version 1.1

  • New skins
  • Add optional server side encryption
  • Unlimited file size upload using HTML5 file API
  • Show speed and estimated time during upload
  • A lot of fixes
  • A lot of new langages
  • Small API to upload files
  • Limit access to Jirafeau using IP, mask, passwords
  • Manage (some) proxy headers
  • Configure your maximal upload size
  • Configure file's lifetime durations
  • Preview URL
  • Get Jirafeau's version in admin interface

Version 1.2.0

  • Link on API page to generate bash script
  • More informative error codes for API
  • Security Fix: Prevent authentication bypass for admin interface
  • CLI script to remove expired files automatically with a cronjob
  • SHA-256 hash the admin password
  • New theme "elegantish"
  • Fix for JavaScript MIME-Type, prevents blocking the resource on some servers
  • Show download link for a file in admin interface
  • Default time for expiration (set to 'month' by default)
  • New expiration time: 'quarter'
  • A lof of translation contributions
  • Code cleanups

Version 2.0.0

  • Various documentation improvements
  • Simplify automatic generation of local configuration file
  • Set a custom title
  • Bash Script: Enhanced help, show version, return link to web view as well
  • »Terms of Service« refactored - Enable admin to overwrite the ToS, without changing existing source code → breaking, see upgrade notes

Version 3.0.0

  • Remove XHTML doctype, support HTML5 only → breaking change for older browsers
  • Remove redundant code
  • Remove baseurl usage and set absolute links instead, which for example fixes SSL issues
  • Extend contribution guide
  • Switch to PSR-2 code style (fix line endings, indentations, whitespaces, etc)
  • Declare system requirements
  • Catch API errors in upload form
  • Allow clients to upload files depending on IP or password
  • Set UTC as timezone to prevent date/time issues
  • Show readable date & time information
  • Fix UI glitches in admin panel and upload form

Version 3.1.0

  • Fix regression on user authentication (see #113)
  • Some cosmetic change

Version 3.2.0

  • Update translations from Update translations from weblate
  • Better style
  • Fix regression on admin password setting

Version 3.2.1

  • fix download view after an upload

Version 3.3.0

  • Added Docker Support
  • Added a copy button next to links to copy URLs in clipboard
  • Now use a delete page to confirm file deletion (#136)
  • Fixed object ProgressEvent Error (#127)
  • Added configuration tips for web servers
  • More translations
  • Style fixes
  • Removed useless alias API support (some old toy)

Version 3.4.0

  • Add encryption support in bash script
  • Refactoring of lang system for simpler management
  • Removed installation step asking for language
  • Merged weblate contributions
  • Fixed some spelling issues