Skip to content
MacIn development · no release date announcedmacOS 14+

Silo Veil · Help & support

A file, a batch, a question.

Start with a copy. Check what changed. Keep the original.

Requirements and availability

Silo Veil is coming soon for Apple silicon Macs running macOS 14 or later. The planned price is $24.99 USD, paid upfront, with no subscription. Processing runs on your Mac without an account, analytics, cloud service or model download.

Process a file or a batch

  1. Choose Add files, drag files into the window, or use File → Add Files or Folders. Enable Include subfolders before importing a folder if you want recursion. Hidden files and symbolic links are skipped.
  2. Select an item and open Inspect. Choose Clean, Mark or Reveal and configure the operation. One recipe applies to the queued files; incompatible items report their own errors.
  3. Choose an output folder, then Process queued files. Silo Veil creates new files and resolves naming collisions without replacing your originals.
  4. Read each result and its warnings. Select Output to preview a completed copy, or Show exported file to reveal it in Finder.

Pause after file finishes the active item before pausing. Resume continues the queue; Cancel requests cancellation. Completed results remain available. Retry failed queues failed or cancelled items again.

What metadata cleanup does

Select supported categories such as location, author, device, timestamps, software, prompts, thumbnails, custom fields and provenance. Color profiles, orientation and format-essential fields are retained where supported. Some composite blocks are handled together.

Cleanup is not content redaction or proof of anonymity. Visible names, document comments, tracked revisions, unknown fields and embedded objects can remain. Finding no supported fields does not prove that a file contains no identifiers. Inspect the result and its visible content before sharing.

Enter an existing PDF password under Document protection. PDF encryption and permissions are retained; older encrypted PDFs may need to keep their first identifier, and the result explains that exception. Editing a signed file requires consent to an unsigned copy. Encrypted Office package cleanup is unsupported; those files can still be packaged unchanged.

Clean pasted or document text

Choose Pasted text, then Conservative text cleanup. Expand Removal positions in context to see visible markers for each removed character. Pasted results stay in the session until you copy them; a remembered output folder does not save them automatically. File cleanup shows each document's proposed removals before export and checks that the file still matches the preview.

The separate document-text operation supports text nodes in DOCX, XLSX, PPTX, ODT and EPUB. Ordinary metadata cleanup does not change document text.

This removes a leading byte-order marker, soft hyphens and eligible zero-width spaces in Latin text. Meaningful joining controls, bidirectional controls and emoji sequences remain. Invisible characters do not establish who wrote a text. Review code and multilingual content carefully.

Visible marks and region repair

In Mark, choose Visible watermark and enter text or choose a logo. Adjust font, size, color, opacity, stroke, rotation, repeated patterns and placement. Presets remember styling; choose the logo again when needed. The final metadata policy runs after visible editing.

Edited raster images export PNG with explicit conversion consent. PDF marks are overlays that retain the original page content. Video edits re-encode and may change quality, size, codec and color; set the start and end time, then check the output for timing, orientation and audio synchronization.

Fill selected region reconstructs an image patch from nearby pixels; video repair covers up to 16 regions or estimates content from their surrounding edges during the chosen shared time range. Neither recovers the original scene. Known corner profile supports specific calibrated visible profiles and must pass its confidence checks. General object inpainting, arbitrary invisible-watermark removal and authorship detection are not included.

Encrypted notes and recovery

In Mark, choose Encrypted hidden note, select a carrier, enter the note and confirm its passphrase. Use several unrelated words. Passphrases must be 20–256 UTF-8 bytes after Unicode normalization; accented and non-Latin characters may occupy several bytes. There is no password recovery.

  • Pixel notes require a single-frame, opaque, 8-bit RGB/RGBA PNG. Sample notes require little-endian RIFF PCM WAV with 16-, 24- or 32-bit integer samples.
  • Text notes append a marked zero-width sequence to TXT, Markdown, HTML or LaTeX prose. Source-code and structured-data files use encrypted packages instead. PDF, DOCX and supported video containers hold a discoverable encrypted record; this is distinct from pixel or sample steganography.
  • Any supported regular file can be stored in a new encrypted .veil package with its note. Restore the package to recover its original contents and filename. Permissions and original filesystem metadata are not restored.

If you allow conversion to a PNG carrier, review the per-file consequences first. Listed precision, transparency or color losses require a separate approval checkbox before creating the copy.

Keep the exact, unmodified output. Resizing, screenshots, cropping, normalization, editing, recompression, social uploads and transcoding may erase a note. Silo Veil recovers its own authenticated notes from supported unmodified carriers; it does not decrypt another provider's scheme.

Use Reveal → Decrypt our note with the matching carrier and passphrase. Wrong passwords and damaged ciphertext fail authentication. Remove our note makes a copy without the recognized record. Removing a pixel or sample note clears its occupied bits; it cannot restore their exact values before embedding.

Supported formats and limits

InputSupported work and limits
TextPasted text and eligible UTF-8 prose: conservative invisible-character cleanup and Silo Veil text notes. Source-code and structured-data files use encrypted packages for notes. Text inspection and cleanup are limited to 8 MiB.
PDFSelected properties and XMP, supported embedded-image metadata, visible text or logo overlays and an encrypted note attachment. Page text, comments, forms and other attachments remain.
DOCX, XLSX, PPTX, ODT, EPUBSupported package properties, ZIP timestamps and identifier fields, plus a separate conservative document-text cleanup. DOCX also supports an embedded encrypted note. Required EPUB structural fields, including its modification timestamp, remain.
Legacy DOCSupported author, last-editor, title and time properties. This does not remove all revisions, comments or document text. Encrypted legacy DOC cleanup is unsupported.
PNG, JPEG, WebP, GIF, TIFFFormat-specific metadata cleanup. Visible editing requires a supported single image and exports PNG. Multiple frames/pages and unusual encodings may limit an operation.
BMP and SVGBMP can be validated and copied; no removable metadata fields are claimed. SVG cleanup handles supported metadata and editor fields, retaining visible text and external references. SVG is not supported for raster editing.
HEIC, HEIF, AVIFNative metadata handling and supported raster conversion. Unsupported codec or metadata layouts produce an error rather than an unverified copy.
MP4, MOV, M4VExposed container metadata, timed text or logo overlays, multiple region covers or edge fills, cover-art replacement and an encrypted container note. Visible edits re-encode video. Private codec or container fields may remain.
WAV, AIFF, FLAC, MP3, M4ASupported audio tags and container metadata. Sample-based hidden notes require supported integer PCM WAV. Protected media and unrecognized tag layouts fail explicitly.
Other regular filesEncrypted .veil packaging and byte-exact file-content restoration. This does not provide universal metadata cleanup or embed a hidden note inside every original format.

Document, package and audio operations accept files up to 512 MiB, with additional archive-entry and expansion limits. Native images are limited to 512 MiB encoded input, 64 megapixels per frame and 256 frames/pages; visible editing needs a supported single image. Pixel notes are limited to 32 megapixels and 256 MiB. Sample notes accept supported PCM WAV up to 512 MiB. Float, 8-bit, compressed, RF64 and extensible WAV are unsupported carriers.

A .veil package can stream one regular file up to 1 TiB, subject to available disk space, with a note up to 1 MiB. Text-note carriers accept up to 48 MiB with up to 1 MiB of ciphertext, subject to expansion capacity. Carrier capacity may impose a smaller limit. Unsupported files and conversions produce an explanation; they are not silently treated as a success.

Inspection recognizes supported note envelopes but does not authenticate them. Automatic detection skips files over 16 MiB or PNG images over 4 megapixels; explicit decryption retains the larger carrier limits above. Source-code and structured-data cleanup preserves literal content. HTML code and preformatted contexts remain protected.

Preferences, clipboard and troubleshooting

Settings can remember your output folder using macOS file permissions. Forget folder removes that remembered access. Presets remain local; passwords and private notes are not saved in settings. Clear passwords and revealed text clears the current secret and result fields. Clipboard contents remain until you replace them, and exported files follow your own sharing and backup settings.

If an operation fails, read its per-file message first. Check the format, selected operation, available capacity, password and conversion consent. For more help, open Help → Silo Veil Help in the app or email the message, app version and file format. Do not send private documents or passwords.

Email support

admin@ohmslaw.net

Include your macOS version and what you were trying to do. A small, non-sensitive sample is useful only if we ask for one.