When sharing travel photos, event records, inspection images, or a portfolio, a plain image folder does not preserve much context, while distributing a separate viewer makes the package more complicated. Bundling the photos and viewer into a single HTML file lets the recipient open one file directly in a browser.
Because the image data is embedded inside the HTML, the output grows as more and larger photos are added. This guide explains the tradeoff between preserving original bytes and using WebP reduction, along with ordering, chapters, comments, and metadata checks before sharing.
Why use a single-file HTML album
A traditional HTML gallery often depends on a separate image folder plus CSS and JavaScript files. A self-contained HTML album embeds the images and viewer together, so it can be stored or moved as one file without broken relative paths or missing assets.
The recipient does not need a dedicated application; a modern browser is enough. This is useful when you prefer to transfer the album through a USB drive, shared folder, or another file-transfer method instead of uploading the photos to a cloud album service.
Choose original images or WebP reduction
Original mode embeds the full JPEG, PNG, or WebP bytes without re-encoding them. It is suitable when you want to preserve image quality or allow the embedded image to be saved again in its original format, but high-resolution collections can make the HTML very large.
WebP reduction can lower the album size by changing the maximum dimensions and quality. This is useful for phone viewing or larger collections, but the images are re-encoded, so it serves a different purpose from preserving the originals exactly.
Use ordering, chapters, and comments to preserve context
A practical workflow is to sort by capture time or filename first, then correct only the places that need manual reordering. Chapters based on days, work stages, locations, or subjects make collections of dozens of images easier to follow.
Comments can preserve brief context such as location or work notes that is not visible in the image itself. The generated viewer can show or hide chapter titles and comments, which makes the same album useful for both records and presentation.
Check output size and metadata before sharing
With embedded images, the final HTML size affects memory use and viewing comfort. OneFile Album shows an estimated output size; when it becomes too large, use WebP reduction or split the collection by subject or time period. Splitting is especially worth considering when the estimate exceeds roughly 250 MB.
When original image bytes are embedded, metadata such as GPS or EXIF that exists in the source file may be preserved as well. Before giving the album to someone else, inspect location and device information when privacy matters.
Step by step
- Open OneFile Album and add JPEG, PNG, or WebP images with the picker or drag and drop.
- Choose whether to preserve the original images or use WebP reduction, then review the estimated output size.
- Sort by capture time or filename and manually drag only the images that need a different order.
- Add chapter breaks, image comments, an album title, and viewer settings as needed.
- Check the final preview, generate the HTML, and review both file size and photo metadata before sharing it.
OneFile Album
Bundle local images and a responsive viewer into one portable, self-contained HTML album.
Tips and limitations
- Before adding a very large collection, test a few images to find a useful balance of quality and output size.
- A simple rule is to favor original mode for preservation and WebP reduction for lighter viewing or distribution copies.
- Original-byte mode may preserve metadata, so inspect GPS and EXIF before creating an album for sharing.
Frequently asked questions
Can the generated HTML be opened without a dedicated app?
Yes. The image data and viewer are included in the HTML, so the generated file can be opened directly in a modern browser.
Are the photos uploaded to a server?
No. Loading images, WebP conversion, ordering, previewing, and HTML generation are performed locally on the device.
How large can the HTML album be?
There is no universal hard limit; practical capacity depends on device memory, browser behavior, and image resolution. OneFile Album recommends splitting the collection when the estimate exceeds about 250 MB.
Can I edit the album again later?
Yes. A compatible OneFile Album HTML can be reopened to restore images, chapters, comments, the title, viewer settings, and other editing data.