How Aftermath handles files and reviews sources.

Choose once, switch tools, replace easily

Selected files stay available when you switch compatible tools in the same group: images, PDFs, video, or audio. The file row shows what is selected and lets you remove it.

• Use × to remove one file. Use Clear all to clear a batch.
• Removing a selection does not delete the original from your device.
• PDF edits belong to the current tool. A prompt asks before you discard them.
• A refresh or closed tab clears selected files. Saved shortcuts contain tool IDs only.

Image processing stays in the browser

When you choose a JPG, PNG, or WebP image, the image workflow decodes it in the browser, renders the requested canvas, encodes a new file, and reports the resulting dimensions and bytes. Selected image files are not sent to an Aftermath server for transformation. The source file is not overwritten; a processed result is offered as a separate download.

• Exact output dimensions and byte checks are measured from the newly encoded browser result, not estimated from a quality setting.
• Crop, fit, padding, rotation, output format, and quality are choices in the local image workflow.
• A browser can still run out of memory or reject an unsupported source. The tool shows an error instead of silently claiming a successful output.

PDF merge, split, and overlays run in the current tab

The PDF workspace reads the selected PDF bytes in the current browser tab. Merging copies source pages into a new PDF in the order you set. Splitting packages new PDFs in a ZIP: leave the selection blank for one output per source page, or enter comma-separated pages or page ranges for one output per entry. The PDF editor can add new text boxes and freehand drawing as flattened overlays in a separate download; it does not rewrite existing PDF text. These file operations do not use an Aftermath server-side document job, and the original files are not altered.

• Merge order follows the visible queue, which supports drag-and-drop and keyboard move controls.
• Split accepts page numbers and ranges. A blank selection creates one output PDF per source page; each comma-separated selection creates one output PDF.
• The editor adds text boxes and pencil strokes as permanent page-content overlays. It does not replace existing text, redact content, perform OCR, preserve forms, or preserve signatures.
• Encrypted, permission-restricted, interactive-form, signed, malformed, or unsupported PDFs are not processed in the workspace. This prevents a broken or unverifiable output.

Video work stays on this device when a browser supports it

When you choose a common MP4, M4V, MOV, or WebM file, the Video workspace reads the required local file regions in the current browser. It inspects first, chooses the smallest supported operation, writes a separate result locally, and reinspects that result before download. It does not send selected video bytes to an Aftermath media-processing service.

• Codec and hardware support vary by browser, operating system, and device. A local limitation is shown clearly instead of using an upload fallback.
• High-resolution video can require substantial battery, processing time, and local browser storage. One active video job and one source file are used per tab.
• The initial local writer holds one completed result in browser memory before a user-selected save or download. It therefore limits source files to 500 MB for output tasks; inspection remains available for larger accepted sources.

Audio processing stays in a local worker

When you choose a supported audio source up to 512 MiB, or a local video for audio extraction within that same source safeguard, the Audio workspace inspects its primary audio track and runs decoding, signal processing, MP3 or WAV encoding, and completed-result verification in a dedicated browser worker. The source remains unchanged and the result is offered as a separate download.

• A selected audio source is not sent to an Aftermath processing service or an upload fallback.
• The worker checks the container and primary track locally. A source with no supported, decodable audio track produces an explicit error.
• Completed outputs are MP3 or 16-bit PCM WAV. The worker checks the output container and reopens the result before enabling download.
• Speech cleanup uses lightweight filters and downward expansion rather than AI separation, and silence shortening uses signal level rather than speech recognition.

Working limits are safeguards, not promises

The current image renderer rejects a requested canvas above 32,767 pixels on either side or above 64 million total pixels. When no fixed output dimensions are supplied, very large images can be capped to a 24 million-pixel working budget. Browser and device memory can impose a lower practical limit.

• The PDF workspace accepts up to 25 PDFs, up to 100 MB per file, and up to 300 MB across the selected batch.
• It checks each input PDF for no more than 1,000 pages, limits a merge to 2,000 pages, and limits a split source to 50 MB and 250 output PDFs per operation.
• The PDF editor accepts one flat PDF up to 25 MB and 50 pages, and limits a document to 100 additions (50 on one page), 500 characters per text box, 5,000 text characters total, bounded pencil points, 15 history snapshots, and a two-million-pixel preview canvas.
• The Video workspace accepts one common source up to 4 GB for local inspection. Its initial bounded-memory writer accepts source files up to 500 MB and validates the completed result before enabling download.
• The Audio workspace allows one active job per workspace, rejects source files above 512 MiB, and holds one completed result in browser memory. It also rejects an estimated or completed output above its 512 MiB buffered-result safety limit.
• These are current application safeguards. They do not guarantee that every file, browser, or destination will accept a result.

How requirement sources are reviewed

Aftermath links platform-oriented presets to the relevant official documentation and records a last-verified date in its public source catalog. Those links explain where a preset came from; they are not a claim that Aftermath controls Apple, Google, YouTube, or any other destination’s acceptance rules. Check the current official rule before submitting a file.

• A source link is shown with affected platform presets so the original requirement can be reviewed in context.
• The public catalog identifies the source, the last-verified date recorded for it, and the part of the product that uses it.
• When a source changes or is ambiguous, use the destination’s own documentation as the final authority.

How quality and correctness stay visible

Public route pages describe the supported input, expected result, browser limits, privacy boundary, and relevant source context in ordinary language. Internal engineering records remain separate from that page copy. When a route or source changes, the public explanation, structured data, and freshness date are reviewed together.

• Route copy is checked against the behavior and limits that the user can actually encounter in the browser.
• Visible titles, descriptions, headings, answers, and structured data describe the same page rather than competing versions of it.
• External rules link to the publisher and state the review boundary; a local measurement never promises external acceptance.

What this page cannot promise

Browser support, memory, codecs, device permissions, third-party policies, and destination review can change outside Aftermath. A clear local result is useful evidence for the next decision, but it is not a universal compatibility certificate or a guarantee that another service will accept the file.

• Keep the source file and review a separate result before replacing or submitting anything.
• Check the linked official publisher when a requirement is time-sensitive or destination-specific.
• Report an inaccurate page or source so the public explanation can be corrected without sending a private file.

Corrections and contact

To report an inaccurate requirement, explanation, or source link, email contact@aftermath.cc with the affected page URL, the authoritative source URL, and a short description of the correction. This gives the issue enough context to review without asking you to send the file you were preparing.