Encode

Encode is the workflow for creating .avk archives. It takes selected files and folders, prepares the archive payload, applies the chosen protection settings, and writes the resulting Avikal container.

The page is designed for both simple archives and larger archive sets. Users can start with ordinary file selection and then add protection options only when the archive requires them.

File And Folder Selection

Users can add individual files, multiple files, folders, or mixed file and folder sets. The staging list supports:

• drag and drop
• add files
• add folders
• search or filter staged items
• select individual items
• select folders and descendants
• delete selected items
• clear all staged inputs
• exclude nested files or folders before archive creation

This staging behavior is important for larger archive sets because users can remove nested items without rebuilding the entire selection from the beginning.

Plain Archives

Encode can create an archive without password or keyphrase protection. This still packages the files into the Avikal container format, but it does not require a user secret during unlock.

Plain archives should be understood as packaging without user-secret access control. Users who need secret-based unlocking should enable password, keyphrase, or other protection options before creating the archive.

Password Protection

Users can enable password protection for an archive. The interface requires a stronger password shape:

• minimum 12 characters
• uppercase letter
• lowercase letter
• number
• symbol

The backend also validates password strength before creating protected archives. This keeps the validation from being only a frontend convenience.

21-Word Devanagari Keyphrase

Avikal supports a 21-word Hindi or Devanagari keyphrase path. This keyphrase can be used alone or together with a password, depending on the selected protection shape.

The app includes:

• keyphrase generation
• copy action
• regeneration
• 21-word validation
• roman typing helper support during decode and rekey

The keyphrase is still a required user secret when the archive is created with keyphrase protection. It should be stored with the same care as a password.

Dual Protection

When password and keyphrase are both enabled, the archive requires both during unlock. The UI warns users that both secrets must be preserved.

This mode is useful when the user intentionally wants a dependency on two separate user-held secrets. It also means losing either required secret can make the archive inaccessible.

Optional PQC Protection

Encode can enable PQC protection for archive key material. Avikal supports two storage choices:

• embedded PQC bundle inside the .avk
• external .avkkey bundle stored separately

Embedded mode keeps the required PQC recovery material inside the archive file. External mode separates possession between the .avk archive and the matching .avkkey file.

External .avkkey Password

For external PQC mode, users can optionally add a separate .avkkey password. This adds a second password layer around the external keyfile while keeping normal external .avkkey behavior available by default.

If this option is used, the user must keep track of the archive, the external .avkkey, and the .avkkey password.

Trio Protection

When password, keyphrase, and PQC are all enabled, the archive requires all relevant unlock material. The UI presents this as a stronger protection state and warns the user to store every required secret safely.

This mode should be chosen only when the added operational responsibility is acceptable.

Large Archive Handling

Encode supports large files and multi-file sets through streaming payload processing. The newer flow writes encrypted payload data directly into a temporary final archive and atomically renames it after successful completion.

This reduces unnecessary extra disk writes and improves crash safety compared with workflows that duplicate large encrypted payloads during finalization.

Adaptive Compression

Avikal can skip compression for known already-compressed formats or large incompressible inputs. This avoids spending time on files such as installers, archives, media, or other data that would not compress meaningfully.

Compression behavior is an optimization. It does not replace the archive protection choices selected by the user.