Make your media library useful before it gets bigger

Name the thing someone will search for

Use the subject, a distinguishing detail and an occasion or date when it helps. Oat-bowl-side-view-autumn is easier to recognise than IMG_4821. Keep names readable and consistent enough that another person can follow the pattern. You do not need a complicated code for every department, campaign and export size.

In Billion’s Add image modal, set the file name and title before saving. Give the title the words a teammate would naturally use when searching. The file name can be more systematic; the title can read like a label. After saving, the image appears in the library grid, where you can open its details and edit the metadata later.

Give each field a different job

The title identifies the image. The description can retain useful context, such as the product shown, the shoot date or a restriction supplied by the rights holder. Keep permission records in your team’s agreed system as well; a description field by itself is not proof of a licence. Upload only material you are authorised to use.

Alt text has a different purpose. W3C’s image guidance explains that a text alternative should communicate the information the image contributes in its context. For a product photograph, that might be Moss-green ceramic bowl with a wide, shallow rim. A list of search keywords would do little to explain the picture to someone who cannot see it.

The same image can need a different description when its job changes. A general photograph of a workshop may be decorative on one page and evidence of a particular technique on another. Treat the library’s alt text as a considered starting point. Check the final destination’s accessibility controls rather than assuming a saved library field is automatically applied everywhere.

Keep the original and choose the right format

Save a dependable original before making crops, overlays or export variants. A square crop for a post and a wider image for a page are separate uses of that original. Give the variants names that explain the difference. Avoid editing the only copy of a photograph until it is impossible to recover the composition you started with.

Billion’s private image library accepts supported static PNG, JPEG and WebP files within its upload limits. The post editor also supports an uploaded H.264 MP4 video, subject to its own size, duration and media requirements. Check the current file guidance before exporting. A file accepted for storage may still need another format for a particular publishing destination.

Attach with a story in mind

You can select media from the post editor or upload there while working on a draft. For one photograph, choose the image that makes the subject understandable immediately. For a carousel, give the sequence a reason: introduce the whole, show the important detail, then show it in use. Remove any slide that repeats the previous one without adding information.

Save the post after choosing and ordering the attachments. Billion retains their references and metadata with that saved revision, so the reviewer sees the package being discussed. Reordering or replacing an attachment changes the post and requires a fresh review. Removing an image from a draft does not delete its original from the library.

Make finding files a small routine

Before an upload session, decide which files are worth keeping. Put near-duplicates side by side and choose intentionally. A collection of four strong product views is easier to use than thirty nearly identical frames whose differences nobody can explain. Keep any necessary production archive separately from the working selection.

Use Grid when visual recognition is fastest and List when names and details matter. Billion’s search and type controls work on the loaded library entries, so load further pages when you are looking for something outside that selection. A search with no visible result should prompt a check of the loaded collection before another person uploads a duplicate.

Finally, review the brand context before adding files. Each Billion library belongs to its brand, with access controlled by the team’s permissions. A little care at that point prevents the wrong logo, a client’s private photograph or an outdated product from becoming the next post’s starting point.