filepack (.fp)

Filepack, file format

A filepack uses the .fp extension to group files under one entry in the Lokad file tree. It can contain any file type; image catalogs are a common use. The pack stores an index of entries whose contents reside in the same account. It is not a self-contained archive: downloading or sharing the .fp file alone does not copy the entry contents.

Paths and updates

Writing to an entry path replaces that entry and preserves the others. Writing directly to the .fp path replaces the whole file. Entry paths are supported by file uploads and transfer destinations. The Pack folder action creates a sibling .fp file from an existing folder, including its subfolders, without deleting the source files.

Only the pack appears in the file tree. Its preview lists the entries and supports filtering by path prefix and downloading individual entries. Access to an entry depends on the user’s file permissions; access to selected entries does not necessarily grant access to the whole pack.

Envision access

• read images reads image metadata and embeddings from a pack. Its image-processing limits are separate from the pack limits.
• downloadUrl accepts an entry path and returns a link to that entry’s content, for example for an image tile.
• previewUrl accepts an entry path and returns a link to its preview. Path-based links resolve the current entry when opened.

Packed entries are not general-purpose tabular read inputs. The .fp extension is not a write output format for Envision tables.

Limits

• At most 200,000 entries per pack.
• At most 256 UTF-8 bytes per relative entry path, including subfolders and filename.
• Entries have no individual modification dates; the transfer Newer flag is not supported for packed destinations.

See store product images in filepacks for creation and dashboard examples, and transfer syntax for packed download destinations and partial-failure behavior.