Straight answers, without the runaround.

Use the Solid Code entry box on the SolidFish landing page. Enter the complete code and continue. The Open a code navigation action returns to that box and focuses it.

For privacy, the same unavailable response may cover an invalid, expired, deleted, or already-consumed package. Check the code, then ask the sender for a new one if access is still required.

A recipient password is an optional credential selected by the sender. It protects package opening and is separate from the Solid Code and management key.

A management key is a system-generated sequence of memorable words and digits shown to the sender after activation. Together with the Solid Code, it authorises actions such as extending expiry or deleting the package.

The raw management key is not retrievable from the server. The sender should store it securely when shown. A protected local-save option may be available on supported devices.

The sender chooses one of the available expiry windows before activation. The exact expiry is displayed to the sender and recipient. One-time completion or sender deletion may make it unavailable earlier.

The sender can use the Solid Code and management key to select a later expiry, provided it remains within the service maximum retention limit.

A one-time package can be completed once. The recipient is warned before claiming it. If the claim has already completed, the sender must create a new package.

Original uploads remain distinct from generated previews. A preview may be created for safer or more convenient viewing, but the interface labels it separately from the original.

SolidFish can show destination information and, where available, a restricted preview before you choose to visit a shared link. That extra inspection step can help people spot misleading or unexpected destinations and build safer sharing habits. It is not a guarantee that a destination is safe, and a website can change after a preview is generated.

Yes. The sender can add multiple optional recipient email addresses. Each message contains the same Solid Code. Passwords and management keys are not included.

Recent-code history is a local browser shortcut list. It is not synchronised to SolidFish or another device and can be cleared from the browser interface.

Use Contact and choose Unsafe or abusive content. Include the Solid Code and a clear reason, but do not send passwords, management keys, or unnecessary copies of private content.

Current size, item-count, file-type and retention limits are shown in Create before activation.

A standard SolidFish handoff does not require a public profile or account, and the sender and recipient do not need to exchange personal contact details just to use a Solid Code. That supports more private, identity-light sharing, but it is not a promise of network anonymity: SolidFish may still process limited technical and security metadata needed to operate and protect the service.

A Solid Code is a short nine-character reference used to open a share. It can be read aloud, written down, or passed through another trusted channel without requiring the sender and recipient to first exchange personal contact details.

No account is required to create or open a standard SolidFish share. A Solid Code can complete the handoff without creating a public profile or account relationship.

A package can contain supported files, a note, and web links. Current limits and accepted file types are shown before activation.

The public web experience is designed for modern desktop, tablet, and mobile browsers.

Because useful-for-now should not automatically become stored-forever. SolidFish gives shares an intentional lifetime so fleeting information can disappear when its purpose has passed. That also reflects our environmental principle: unnecessary digital copies still rely on physical storage infrastructure, so avoiding indefinite retention where it is not needed is a small but worthwhile habit — every little helps.