Attachments

A PDF can carry other files: a spreadsheet with the numbers behind a report, the original of a scanned contract. They sit in two places: the document’s own attachments, and file attachment annotations, a file pinned to a spot on a page. Register attachmentPlugin() to list both as one list:

<script lang="ts">
  import {
    displayNameOf,
    useAttachment,
    useAttachmentState,
    type AttachedFile,
  } from '@embedpdf/svelte/attachment';
  import { saveFile } from '@embedpdf/svelte/runtime';

  const attachment = useAttachment();
  const state = useAttachmentState();

  async function save(file: AttachedFile) {
    const { bytes, name, mimeType } = await attachment.download(file);
    saveFile(bytes, name, mimeType ?? undefined);
  }
</script>

<ul>
  {#each state.files as file (file.id)}
    <li>
      <bdi>{displayNameOf(file)}</bdi>
      <button disabled={!state.canDownload} onclick={() => save(file)}>Save</button>
    </li>
  {/each}
</ul>

What useAttachmentState() gives you updates by itself: after your own changes, and on a shared document, after someone else’s. Nothing is read when a document opens: the attachments load the first time something asks for them. The files on the pages come from the annotation plugin, when you’ve registered it.

Show the files#

files lists the document’s attachments first, in the order the document keeps them (by name), then the files on its pages, in page order. Each file has its name, mimeType, description, size, checksum, createdAt and modifiedAt (null when the PDF doesn’t say), an id for your list’s keys, and its home:

• { kind: 'document', ref }: one of the document’s attachments, ref its name in the document.
• { kind: 'page', ref }: a file attachment annotation; ref.page is its page.

Show a name with displayNameOf(file), and put it in a <bdi>. A name can hide characters that make it look like another (invoice.pdf that is really invoice.exe); displayNameOf takes them out, and the <bdi> keeps a name in another script from turning your row around.

status says whether the attachments haven’t been asked for yet ('idle'), are loading, are there ('ready'), or couldn’t be read.

Save a file#

download(file) returns the file’s bytes, its name ready to save under (displayNameOf‘s) and its type. Hand them to saveFile() to save them as a browser download:

const { bytes, name, mimeType } = await attachment.download(file);
saveFile(bytes, name, mimeType ?? undefined);

Save a file; never open it in a new tab or a frame of your page. A file opened there runs with your page’s origin, so an HTML attachment could act as your page.

Saving takes a file out of the document, so it needs doc.download: check canDownload. A file too large to unpack in the browser is refused (see Large files).

Attach files#

add(files) attaches files as one change: one step to undo. A File the user picked brings its name and type; bytes need a name:

await attachment.add([{ data: picked }, { data: bytes, name: 'figures.csv' }]);

Names are unique in a document: a name it has already gets a number, notes (2).txt, so nothing is replaced. The files show at once, isPending(file) while the engine saves them, and add() resolves with them. Check canAdd first.

Remove a file#

remove(file) takes a file away, as one step to undo: an undo brings back the same file, with its bytes and dates. A file on a page goes with its annotation, through the annotation plugin. canRemove(file) says whether this one may go.

<script lang="ts" module>
  import { DocumentGate, Viewer, type OpenInput } from '@embedpdf/svelte/runtime';
  import { RenderLayer, renderPlugin } from '@embedpdf/svelte/render';
  import { Stage, stagePlugin } from '@embedpdf/svelte/stage';
  import { attachmentPlugin } from '@embedpdf/svelte/attachment';
  import { cloudEngine } from '@cloudpdf/engine';
  import Files from './Files.svelte';

  import '../files.css';

  const engine = cloudEngine();
  const plugins = [stagePlugin(), renderPlugin(), attachmentPlugin()];

  const welcome: OpenInput = { kind: 'grant', grant: 'shr_gvpJcG1ULUMon19C0D1wODSY' };
</script>

<Viewer {engine} {plugins} initialDocuments={[{ source: welcome }]}>
  <DocumentGate>
    {#snippet fallback()}
      <p class="loading">Loading…</p>
    {/snippet}
    <div class="layout">
      <Files />
      <Stage class="stage">
        <RenderLayer />
      </Stage>
    </div>
  </DocumentGate>
</Viewer>

Go to a page’s file#

reveal(file) selects a page’s file attachment annotation and brings it into view, through the stage when you’ve registered it. It does nothing for one of the document’s attachments, which isn’t on a page.

Select files#

select(files) makes files the selection, and selected lists them. The selection is the reader’s: show it, and act on it with your own buttons and menus.

attachment.select([file]);
await attachment.remove(selected[0]);

Methods#

Everything useAttachment() gives you.

Every method that returns a promise also takes a signal in its options, to cancel it.

State#

Everything useAttachmentState() gives you, as one reactive object: read its fields, and your markup updates when they change. The method in the last column reads the same value once.

Events#

<script lang="ts">
  import { useAttachmentEvent } from '@embedpdf/svelte/attachment';

  let notice = $state('');

  useAttachmentEvent(
    (attachment) => attachment.onChanged,
    ({ type, files, origin }) => {
      if (origin.kind === 'remote') notice = `Someone ${type} ${files.length} file(s)`;
    },
  );
</script>

<p role="status">{notice}</p>

type is 'added', 'removed' or 'restored'; for a removal, files are the files as they were. A file on a page is an annotation: its changes are the annotation plugin’s events.

Permissions#

Removing a file on a page is deleting its annotation, so the annotation’s own permission decides: canRemove(file) asks it.

Good to know#

Large files#

The server unpacks the file and applies its own limit; download() rejects a larger one with invalid-input.

Removed files and saving#

Removing a file takes it out of the document as it is now; an incremental save still contains the version you opened. When a file must really be gone, save with mode: 'rewrite'. See Saving.

The ready-made viewer#

The viewer’s Attachments panel is built on this plugin. See Panels.