A closer look at Flare

Explore real screens before you install, or discover a feature you have not tried yet. The walkthrough uses captured app screens; the settings lab runs locally in your browser. Neither connects to a live account.

Explore the workspace

Choose a step, then enlarge the screenshot to inspect the details. The screenshots use demonstration accounts and files.

STEP 1 OF 6 · REAL APP SCREENSHOTS

A home for every file

Filter your library to images and choose Group files → By month in Upload date. Open an image for a closer look, then move through the filtered gallery.

Read the complete guide →

Captured from Flare with demonstration data. Your instance’s appearance and files will differ.

Captured from Flare with demonstration data. Your instance’s appearance and files will differ.

1 / 6

Watch real workflows

These short, silent recordings capture actual browser interactions with Flare and an isolated test database. Playback is manual and downloads only when requested. The written steps below each video are also its descriptive transcript.

Organize and upload

1. In Files, create a folder named Project launch.
2. Select two existing files and move them into that folder.
3. Open the folder and create a Week 39 subfolder.
4. Use Upload here to upload a project checklist into the subfolder.
5. Open the destination from the completed upload.

Moving a file preserves its individual share link. Read the folders guide.

Share a collection, then revoke access

1. Open a folder’s sharing controls and create a share link.
2. Visit the collection as a recipient. Public files appear; a password-protected file appears as a generic locked tile.
3. Return to the owner’s sharing controls and disable the link.
4. Revisit the collection URL to confirm the shared page is unavailable.

Disabling a folder link does not revoke a file’s separate public URL. Understand sharing boundaries.

Open a protected file

1. Open a locked tile from a shared folder.
2. Enter an incorrect password; the file stays locked and its name stays hidden.
3. Enter the correct password to reveal the file and its normal viewer.

This flow is for a public file protected by a password. Private files are not included in a public folder share.

Upload options lab

Try the precedence rules behind account defaults, saved profiles, and per-upload choices. This is an educational model of the upload profile rules, with explicit inputs; it does not read your account.

TRY THE RULESLocal simulation

Change the inputs to see which visibility setting wins. Flare starts with public visibility; make a private profile your default to change your everyday uploads. Nothing is uploaded or saved here.

1. Starting visibilityPublic

2. Saved profileInherit starting visibilityPublicPrivate

3. This uploadUse profile / defaultsPublicPrivate

Use a token bound to this profile

EFFECTIVE VISIBILITY · Starting defaultPublic

People with the share URL can view the file unless it also has password protection.

ExpirationNo expirationAfter an hourAfter a dayAfter a weekAfter a month

When it expiresDelete the fileMake it private

When the expiration worker processes the deadline, the file is deleted. Keep a separate copy if you need it later.

Build an API request

Generate curl, JavaScript, or Python examples with your instance address. The builder never asks for a token and never sends a request.

BUILD YOUR FIRST REQUESTNo requests sent

Choose an operation and copy a working starting point. Set FLARE_TOKEN in your terminal to a named token with the required scope.

Instance URL

OperationUpload a fileList your filesList short linksCreate a short link

POST /api/filesScope: files:upload

curl --fail-with-body 'https://files.example.com/api/files' \
  -H "Authorization: Bearer $FLARE_TOKEN" \
  -F "file=@./screenshot.png"

Credentials never enter this demo. Run these requests yourself against your instance; uploads and short-link creation change your data.