Running an event produces two piles of files: the pack you send before the day, and the media you publish after it. The pack is a merge job. The media is a batch job. Both go wrong when the order is skipped.
Build and merge the pack before numbering it, because page numbers have to match the final page count. Crop and compress badge photos before printing, not after. For the media, compress first, strip metadata second, and add a watermark only to the version you are happy to publish. Every step runs in the browser, so contracts, attendee lists and unreleased photos never leave your machine.
1. Build the delegate pack from files you already have
A delegate pack is rarely one document. It is an agenda from a word processor, a venue map exported as an image, a speaker list someone emailed, and a terms page that legal signed off. Image to PDF turns the images and screenshots into pages, and Merge PDF joins them with the PDFs you already have, in the order you drag the cards.
Merge in reading order: welcome note, agenda, venue map, speaker list, terms. JPG and PNG files are embedded without re-encoding, while WebP, AVIF, GIF and BMP are converted first. There is no fixed file limit, and the practical ceiling is your device memory because every page is held locally.
Two limits. The tools do not design the document, so the agenda still has to come from your editor. And a password protected PDF has to be unlocked before its pages can be read. If the pack will be printed, add page numbers after the merge, so the numbers match the final page count rather than a draft.
Merge PDF
Join the agenda, map, speaker list and terms into one pack, in the order you set.
2. Crop badge photos to one size
Badge photos only look consistent when the crop is consistent. Image Cropper accepts a batch of up to 30 photos and applies the same relative frame to every image, so you set the ratio your badge template uses once and export the whole set with Download all. The output keeps full resolution, which means the printer is the bottleneck rather than the tool.
If the badge template needs one exact pixel size, run the exported set through Image Compressor and pick a fixed width there. Note that Image Resizer handles one image at a time, so it is the wrong tool for a batch of two hundred attendees.
Two limits are worth saying out loud. There is no face detection, so a set with heads in different positions still needs a quick visual pass. And there is no perspective correction, so a photo taken at an angle stays skewed; shoot straight on against a plain background.
Image Cropper
Crop up to 30 photos with the same frame and ratio, then export the batch at full resolution.
3. Publish the event photos
Image Compressor takes multiple files, so the whole gallery can be tuned once and exported together. Keep the quality slider between 75 and 90 for photographs; AVIF and WebP give the smallest files, while PNG with OxiPNG recompresses losslessly and suits slides, signage and screenshots. There is no fixed cap on how many images you add in one run, though a very large set is better handled in a few passes.
Metadata is the part organizers forget. Photos from a phone carry GPS coordinates, and a venue or a speaker's home should not travel with the file. Remove EXIF strips EXIF, XMP, IPTC and comments from JPEG and PNG without re-encoding the pixels, and it lists the coordinates before you commit. The catch is that it handles one file at a time, so a large gallery is slow work. Image Compressor and Image Resizer also drop EXIF as a side effect of redrawing the photo on a canvas, which is faster but re-encodes the image.
Image Watermark places text at one of five positions or tiles it diagonally, with size, colour, opacity and rotation, and it exports a whole batch with one style. Use it on the press preview set, and export clean files separately for the sponsor who paid for the photos. The watermark is drawn into the pixels and cannot be removed later.
Image Compressor
Compress the gallery in one pass, with a quality slider and a live before and after preview.
4. Publish the talks
Video Compressor sets output format, quality, resolution and frame rate, so a 4K room recording can come down to 1080p or 720p for a platform that re-encodes anyway. Clips under 200 MB and a few minutes long are the comfortable range because every frame is processed locally; a full session should be split before it reaches this step. The first run downloads the FFmpeg engine of about 30 MB.
If the source is WebM or MOV, Video Converter rewrites it to MP4 with H.264, which is the safest format for a player you do not control. Captions go through Add Subtitles, which burns SRT, VTT, ASS or SSA into the picture. Two limits there: the renderer bundles one Latin font, so non-Latin scripts are not covered, and the clip is fully re-encoded, so export takes roughly half the video length to the full length.
For an audio feed, Video to MP3 drops the video and writes 192 kbps audio, or 128 kbps for speech. There is no loudness normalisation or chapter marker, so a podcast that needs either has to finish in an audio editor. And none of these tools cuts or joins: trimming a session belongs in Video Trimmer, and combining takes belongs in Video Merger.
Video Compressor
Bring a talk down to a publishable size with format, quality, resolution and frame rate controls.
What this workflow cannot do
- No badge, poster or registration form templates. These tools change files. They do not lay out a badge, design a poster or create a form.
- No face detection or auto-framing. A batch crop uses one fixed frame, so heads in different positions need a manual check.
- No batch renaming. Files keep the names they arrive with, so a numbering scheme has to be applied outside the browser.
- No RAW or HEIC decoding. Camera RAW and phone HEIC files cannot be opened; export JPG or PNG first.
- No batch metadata stripping. Remove EXIF handles one file at a time. A large gallery takes a while, or you accept the re-encode that comes with the compressor.
- No non-Latin captions. The subtitle renderer covers Latin scripts only.
- No target file size. Compression reports what it achieved; it cannot promise a platform's exact limit in advance.
- No publishing. Nothing is uploaded to a platform or sent to attendees. You download the file and distribute it yourself.