Model · DigUp angle

How DigUp uses EmbeddingGemma 2

DigUp’s search quality comes from Google DeepMind’s EmbeddingGemma 2, run on-device through llama.cpp. Your files stay local; the model maps text queries and multimodal content into one ranking space.

Model docs: Google AI — EmbeddingGemma. DigUp project: ARahim3/DigUp. Other apps (e.g. Aether) may also use EmbeddingGemma 2 — this page is DigUp-focused, not a competitor teardown.

What EmbeddingGemma 2 is

EmbeddingGemma is Google’s embedding model family for turning inputs into vectors you can compare. DigUp uses EmbeddingGemma 2 so a typed query can rank photos, PDF pages, document passages, audio windows, and video frames together — not only keyword hits.

One index, many modalities

InputHow DigUp uses the modelYou get
Text queryEmbed query with text tower at search timeNearest neighbors + keyword boost
Images / screenshotsVisual embeddings (OCR text on Mac for scans/screenshots)Find by what’s depicted
PDF pagesPage-level meaning (+ text / OCR where available)Open to the right page
Audio~30s windows in the shared spaceJump near the moment
VideoFrame / moment embeddingsJump near the moment

Local-first implications

  1. First launch downloads the model (~865 MB). After that, indexing and search run on device.
  2. No DigUp account — privacy model is local index + optional update check (can be disabled per upstream docs).
  3. If network blocks the download (Mac 0.6.1) — Settings → Storage → Use Files… to supply the model files DigUp expects.
  4. Hardware — Apple Silicon Metal on Mac; Win/Linux pick GPU when faster and equivalent, else CPU (CPU photo indexing is slower).

Sourced numbers (cite date 2026-10-15)

NumberContextWhere to verify
~865 MBFirst-run model download size DigUp documentsREADME / release notes
~740M paramsEmbeddingGemma 2 scale (Google / DigUp materials)Google AI docs
768-dShared vector space DigUp describesUpstream README
~3,716 starsARahim3/DigUp popularity signalGitHub API