The settings that decide how files are stored, listed and transferred are under Files →
Settings in the control panel, which only the superuser can open. This page covers General,
File list and Advanced. The other three are described with the features they control:
Features — collections, ratings, folder colours and the media libraries. See
Collections, Organizing files and
The media libraries.Searching — see File indexing and full-text searching and
Searching files and folders.Thumbs and previews — see Enabling thumbnails and preview.Keeps a history for each file. See File-based activity logs, which also
covers Number of days to keep the file activity log entries.
When a file is overwritten, FileRun keeps its previous content as an old version, up to this number of
versions for each file. The default is 2, and 0 turns versioning off. See
File Versioning.
Old versions do not count against the storage quota.
A list of file extensions that cannot be stored, such as exe or php. A file with one of these
extensions is refused when it is uploaded, created, renamed or extracted from an archive, through the
web interface, WebDAV, the API or the sync apps. The sync apps receive the list, so they do not even
try. Files that are already stored are not affected.
An account that has its own Allowed file types list, among its upload permissions, is not affected by
this list either: its own list applies instead.
These settings apply to every user.
Default layout — the layout a folder opens in: Compact list, List layout, Thumbnails layout,
Photos layout or Previews. The default is Thumbnails layout. Users can switch to another layout
with the buttons on the toolbar.Show thumbnails in detailed list — shows thumbnails instead of file icons in the list layout. On by
default.Animate thumbnail display — animates the thumbnails while they load. On by default.Double-click files action — what double-clicking a file does: open preview, the default, or
open in browser, which opens the file directly in the browser.Paginate large folders — the number of files per page in a large folder. The default is 300.
Showing more than 1000 items per page can freeze a browser.Hide dotfiles (~/.*) — hides the files and folders whose name starts with a dot, such as
.htaccess. On by default. They are hidden only in the web interface: WebDAV, the API and the apps
still show them, and users can still create or upload them.Number of tags to show for each listed item, Number of tags to show in full text for each listed item and Number of tags to show for a folder in "Thumbnails" mode — how many tags appear next to a
name, and how many of those with their text. The defaults are 2, 2 and 1. See
Organizing files.Lets the web server send the files for download instead of PHP, which is faster for very large files.
The choices are NGINX X-Accell, Apache XSendfile and LiteSpeed Internal Redirect, one for each
web server, and the default, - None -.
Choosing one is not enough. The web server has to be configured for it, and allowed to read the users' files:
Apache XSendfile needs the mod_xsendfile module, with XSendFilePath set to the folder that holds
the users' files. The official Docker image is set up this way.NGINX X-Accell needs an internal location that serves the users' files. The folders it applies to
can be limited with $config['x_accel_paths'].LiteSpeed Internal Redirect needs $config['x_lightspeed_root'], the path that the web server's
redirects are relative to.FileRun uses the accelerator only when the web server really is the one chosen, and sends the file
itself otherwise. If in doubt, choose - None -. After you enable one, check that downloaded files are
complete.
Large files are uploaded in pieces of this size, in megabytes. The default is 98, the lowest value is 20, and the recommended range is 100 to 1000. Bigger pieces are faster on fast connections, but each piece is one HTTP request, and web servers and proxies limit the size of a request:
| Server | Default limit |
|---|---|
Apache, LimitRequestBody |
1 GB |
NGINX, client_max_body_size |
1 MB |
Caddy, request_body {max_size} |
1 MB |
IIS, maxAllowedContentLength |
about 28 MB |
| Cloudflare and similar services | usually 100 MB or less |
With NGINX or Caddy the limit always has to be raised, because even the smallest piece is larger than their default. If large uploads fail, lower this value or raise the limit on the server.
Size of a "small" file, in megabytes. The default is 20 and the lowest value is 5; it cannot be
larger than the chunk size.
When the upload of a larger file is interrupted, it continues where it stopped. A smaller file is simply sent again from the start. Lower the value if your users often upload over slow connections, where a file of this size takes a long time.
Allow file names that end with a dot character and Allow file names that end with a space character are off by default. On a Windows server, the operating system drops the last character when
the file is saved, so the file ends up under a different name. Leave them off unless your server does
not run Windows and your users need such names.