InJest is a Windows app that offloads footage from any kind of card, SD, CFexpress, and drone media alike, verifies every file with a checksum (TrueVerify), and files it automatically into a clean date and type structure. It also covers Projects (searchable client and shoot metadata for everything you've ingested), backup, importing media from a shared link, encrypted peer-to-peer transfer, a Library tab for browsing any drive, and a batch Media Encoder: one app for the whole ingest workflow.

InJest is a native Windows application. There's no macOS or Linux build at this time.

InJest auto-detects cards from Sony, GoPro, DJI, Canon, Fujifilm, Panasonic, Nikon, Blackmagic, and Insta360, and labels them accordingly during ingest. Cards from other manufacturers still ingest normally: with camera folder segregation turned on, they fall back to the card's own volume label (whatever you've named it) instead of a detected camera name, or "Unknown Camera" only if the card has no label at all.

Mostly no. Ingest, checksum verification, local/NAS backup, the Library tab, and the Media Encoder all work fully offline. Backing up to a cloud-sync folder (Google Drive, Dropbox, OneDrive, Proton Drive) is a partial exception: InJest itself writes to that folder offline just fine, but the sync client still needs its own internet connection to actually upload those files to the cloud, so the backup isn't really complete until that sync catches up. Import is the one tab that genuinely needs a connection, since it's syncing media in from a remote link. Beyond that, an internet connection is only needed for signing in/subscription checks and the internet-fallback path of P2P transfer.

Wherever you point it: a local drive, an external drive, or a NAS share you choose. InJest doesn't have a server component that footage passes through, files move directly from your card to the destinations you configure.

Yes. InJest read-tests every source file (first and last chunk) before copying starts, so a bad sector or flaky card is caught upfront instead of failing partway through the copy. A file that fails this check is flagged as unreadable and skipped, the rest of the card still copies. Cards are opened read-only, and reading a card doesn't wear it down the way writing to it does.

A checksum is a unique fingerprint calculated from a file's contents. Every file is first written under a temporary name, then hashed, then re-read from the destination and hashed again. Only once the two fingerprints match exactly, byte for byte, does InJest rename the file to its real filename, a safeguard we call TrueVerify. This catches corruption that a simple size-matching copy (like Explorer's) would silently miss.

Once every file on the card has been copied and its checksum verified, InJest can automatically eject the card so it's safe to pull, instead of you having to remember to eject manually or risking a pull mid-write.

Format Card quick-formats a card: it's destructive and can't be undone. There are two ways to trigger it. Turn on "Format & eject after verified ingest" in Settings and it runs automatically, formatting and then ejecting, but only as the last step of an ingest that finished fully verified. There's also a manual Format button for formatting a card any time (it only formats, it doesn't eject), which shows a confirmation dialog reminding you to make sure the footage was verified first, it isn't blocked by software the way the automatic option is, so use it deliberately. We'd still recommend formatting the card in the camera itself rather than from a PC when you can: it's the format your camera actually expects, and it means the format step doesn't depend on this machine being available and working correctly.

InJest protects against this with what we call TrueVerify: a file only gets its real filename once it's fully copied and checksum-verified; until then it sits under a temporary name. So if you lose power, pull the card, or close the app mid-copy, re-running the same ingest picks up cleanly: anything that already finished is left alone, and anything that didn't is copied fresh. Nothing gets duplicated or skipped.

One primary destination plus up to 3 backup destinations per ingest, 4 total. The source card is read once and all of them are written together in the same pass, so they can't drift out of sync with each other.

Google Drive, Dropbox, OneDrive, and Proton Drive all install a desktop app that mirrors your cloud folder as a normal local folder. Add that synced folder as one of your backup destinations and it's covered exactly like a local drive. InJest has no separate cloud integration: it doesn't call any cloud provider's API, and it doesn't know or care that the folder happens to sync to the cloud in the background.

No, in the strongest possible sense: InJest never authenticates against, logs into, or talks to any cloud provider's servers at all. It only ever reads and writes local folders, including whichever local folder your own sync client happens to be watching.

The Projects tab shows a status per destination: checksum-verified, sizes match, partial, unreachable, or not backed up yet. "TrueVerify Backup" re-hashes both copies and compares them on demand, which catches silent corruption that a plain existence check would miss.

Paste a link, a Google Drive folder shared as "anyone with the link", or a direct media link, and InJest inspects it, shows you the size and file count up front, then syncs it into a local folder, checking each downloaded file's hash against the checksum Google Drive itself reports for it. It doesn't sign in to Google or browse your (or anyone else's) whole Drive: only what a link's own sharing settings already make public. A private or restricted link says so rather than prompting a sign-in.

Both sides run InJest. The receiving side shows an 8-digit connection code; the sending side enters that code and picks projects or files to send. The two machines connect directly, LAN speed on the same network, or a direct internet connection via NAT hole punching off-site, with no relay server in between either way.

It's encrypted, and no, nothing passes through a server. Both sides authenticate directly with each other using the Noise Protocol Framework's XX handshake (the same cryptographic framework WireGuard is built on) before any file data moves, so the connection is end-to-end encrypted device-to-device. There's no central InJest server involved in the connection or the transfer itself.

Batch encode or convert footage using presets (like an H.264 delivery format or a lossless remux) or advanced mode, where you set codec, quality (CRF) or bitrate, and container manually. It runs on the FFmpeg binary bundled inside InJest, with no render cache or intermediate copies, so a batch only ever uses as much disk space as its output files.

Yes. Solo and Duo are both billed monthly or yearly, through Razorpay in India and Paddle everywhere else. There's no lock-in contract: cancel any time from Settings > Account & Subscription and you keep full access through the end of the period you already paid for.

Your trial gives you full, unrestricted access with no limits for 30 days. Your existing projects, settings, and everything you've already done stay exactly where they are: subscribing just unlocks everything again. The trial is tied to your account and device, so it can't be renewed by creating a new account on the same machine.

Yes, once you have a subscription, InJest works exactly the same on any device or setup - a subscription is never affected by this. It's only the free trial that requires your device to be verified as real, physical hardware, since an unverified device could otherwise be reset indefinitely to claim a new trial for free. This can happen on virtual machines, some corporate-managed or locked-down PCs, and other unusual hardware setups. If your device can't be verified, no trial period is available on it, but subscribing works regardless.

Solo covers 1 device signed in at a time, Duo covers 2, every feature is identical across both tiers. Unlike the old license model, there's no permanent binding and no one-time "move" limit: sign out of one machine and into another whenever you like from Settings > Account & Subscription. If signing in on a new device would put you over your limit, InJest asks you to confirm before signing the oldest one out, so you don't lose an ingest that's still running elsewhere by accident. A device that goes offline keeps its slot for 7 days before InJest frees it automatically.

Yes, from Settings > Account & Subscription in the app, or from the pricing page on the website. Upgrading from Solo to Duo takes effect immediately (your Solo plan is cancelled and a new Duo subscription starts right away, no refund for the unused remainder). Downgrading from Duo to Solo cancels your Duo plan at your next renewal, you keep Duo access until then, and picking up Solo afterward is a separate quick subscribe step rather than something that happens on its own.

Razorpay (India) or Paddle (everywhere else) retries a failed renewal automatically over the next few days. You keep full access the whole time, InJest only locks once every retry has failed. Update your payment method via that provider's emailed link to stop the retries and renew normally.

From the pricing page's "Redeem it here" link, or from Settings > Account & Subscription in the app. A coupon gives you a free period before your first real charge, but still requires setting up a real subscription (your payment method is authorized now, nothing charged until the free period ends). Each code works once, for one account.

Only how many devices can be signed in on that subscription at once. Solo is 1 device, Duo is 2, every feature is identical across both tiers.

There's no option for that right now. Team/volume plans beyond 2 devices are being built and aren't available yet. Email support@injest.app if you'd like to be notified when it's ready.

Checkout is handled by Razorpay in India (cards, UPI, netbanking) and Paddle everywhere else (cards and other locally available methods), both for recurring subscriptions. Your subscription activates automatically once your payment provider confirms it.