Prepare the files people need to share your book

Think about the person receiving the files

A person sharing your book may be preparing a newsletter, an event listing, an interview page or a social post. Each task needs a slightly different asset, but all benefit from clear names and accurate information. Assemble the package around those uses instead of sending a large folder of everything produced during the book's development.

Begin with approved cover artwork, the exact title and author name, a concise description and a stable book-page link. Include publication or event details only when they are confirmed and relevant. If a fact is still provisional, do not let it sit in a file that looks ready for public use.

Provide useful versions without creating confusion

A high-resolution front-cover image and a smaller web version can serve different needs. Label them by purpose and keep their proportions intact. Do not ask recipients to extract the front cover from a full print wrap containing the spine, back cover and production marks.

If you provide an author photograph, include its credit and usage conditions where needed. Keep those instructions beside the file. A recipient should not have to search an earlier email thread to discover whether the photograph may be cropped or used in a promotional graphic.

Write a short and a slightly longer description when both have genuine uses. Identify their lengths or intended placement, and make sure they describe the same book consistently. Avoid a collection of nearly identical drafts with no indication of which wording is approved.

Make the package navigable

Use filenames that identify the author, book and asset. “Cover-web.jpg” may be understandable inside your own folder but ambiguous after someone downloads it alongside material for several other books. A modest amount of context in the filename prevents avoidable mistakes.

Keep editable working files separate from ready-to-use outputs. A host preparing an event listing is unlikely to need a design application project. Give them a format suited to the job, and offer further specifications if their production process requires something different.

Include a brief text note with the main facts, relevant links and a contact route for questions. It can also state which files are current. This note should explain the package in plain language rather than reproduce the history of the design process.

Open the exact folder or download link from a signed-out browser when public access is intended. Confirm that files download successfully, images open and the description is readable without specialised software. Check that no private comments, draft claims or personal information have slipped into the package.

When an asset changes, replace it deliberately and tell collaborators who need the correction. Keep enough version information to distinguish the new file. The aim is to make accurate sharing easy: the recipient should spend their time presenting the book, rather than repairing or interpreting the materials you supplied.