LiquidFiles review

LiquidFiles is secure file-transfer server software that runs on your own infrastructure or private cloud. It handles sending, receiving, requesting and sharing files, rather than acting as a general cloud-storage service. The homepage lists no file-size limit, but it does not publish a maximum transfer size there; your practical limit will depend on the infrastructure you provide.

For sending, staff use a webmail-like interface and recipients can download through a secure link without creating an account. Filedrop pages let people upload files without sender accounts. Shared folders support internal or external teams, access controls, expiration dates and download tracking. File requests provide a direct upload link for clients or partners.

The feature set also includes activity logs, download confirmations, geolocation data and compliance reporting, according to the published product information. Authentication options include LDAP, Active Directory, SAML2 single sign-on and built-in two-factor authentication.

LiquidFiles fits organizations that need control over where files go and who can retrieve them. Hosting it on your own infrastructure can keep file exchange within your environment; a commenter on r/sysadmin said that direct transfer between customer and company mattered to them. That is a user’s account, not a guarantee about every deployment or its security.

The practical strengths are:

• External recipients can download files without accounts, and external senders can upload through Filedrop pages.
• Shared folders include access controls and expiration dates, while download tracking and audit logs give administrators a record of file activity.
• LDAP, Active Directory, SAML2 and built-in two-factor authentication give teams options for fitting access into existing identity systems.
• The pricing page lists all features on every user tier, with unlimited external senders and recipients included.

One r/sysadmin thread describes using LiquidFiles to handle large files and reduce sensitive attachments in email. That commenter also said non-technical users found it easy to figure out. These reports suggest a useful fit for controlled business-to-business exchange, but they are individual experiences, not independent security validation.

The main trade-off is operating the infrastructure. LiquidFiles is server software for your own infrastructure or private cloud, and the pricing page says AWS and Azure infrastructure costs are separate. Teams that want a hosted service without managing deployment may find that a poor fit. The homepage lists no file-size limit, but does not publish a maximum, so confirm capacity against your own setup rather than treating that as unlimited storage.

Pricing is based on local-user caps. The pricing page lists annual-billing equivalents of $10.42/month for 5 users, $15.75 for 10, $20.75 for 20, $33.25 for 35, $47.42 for 50, $66.58 for 75, $83.25 for 100, $120.75 for 150, $158.25 for 200 and $208.25 for unlimited users. It lists no monthly billing option; three-year licenses save about 15%, with the 5-user plan at $319 and unlimited at $6,249. There is no free plan, though a 45-day trial is listed. A bookkeeping thread called LiquidFiles potentially overkill for a sole practitioner, a reasonable warning for very small teams.

The pricing page lists annual equivalents from $10.42 per month for 5 users to $208.25 per month for unlimited users. Those are not monthly-billing prices: the page lists annual and 3-year billing, but no monthly option. The 5-user plan costs $319 for three years; the unlimited plan costs $6,249 for three years.

All listed plans include every feature and unlimited external senders and recipients. The tiers cap local users: 5, 10, 20, 35, 50, 75, 100, 150, 200, or unlimited. The price rises by $5 per month equivalent from 10 to 20 users, then by $12.50 from 20 to 35. Check your likely user count before choosing; moving up a tier can cost more than the lower-tier headline suggests. LiquidFiles says 3-year licenses save about 15%, but that means committing for longer. A 45-day free trial is listed. AWS and Azure infrastructure costs are extra and paid to the provider.

Switching to LiquidFiles means choosing where it will run: the product is server software for your infrastructure or private cloud. Plan for that deployment, then check how your existing user directory and sign-in setup will map over; LiquidFiles lists LDAP, Active Directory, SAML2 single sign-on, and built-in two-factor authentication. The published information does not specify migration tools, import formats, or data-export options, so confirm those with the vendor before moving files, user records, permissions, or audit history.

Leaving deserves the same checks. Before committing, ask how to export stored files and logs, whether shared-folder permissions and expiration settings can be preserved elsewhere, and what happens to existing links. Those are migration questions, not documented capabilities in the material available here. We also don’t have Reddit posts or comments in the published material, so we can’t substantiate a claim about why users leave. The clearest reason to look elsewhere is a mismatch with the operating model: LiquidFiles is less suited to buyers who want a lightweight tool or want to avoid managing infrastructure.