DICOM, STL, PLY, OBJ, JPEG, PDF, up to the big multi-hundred-megabyte CBCT exports that bounce off email servers.
Files are encrypted in your browser before upload and the key travels in the link fragment. It never touches our servers. Email attachments can't say that.
Recipients click a link and download. No account, no portal login, no fax machine screaming in the corner.
Drop the files (or a zipped CBCT export) on send.intake.dental
Copy the secure link: the decryption key rides along in it
Text or email the link to the office, lab, or patient
Yes. Send is free for every dental office, lab, and patient. It's how we introduce ourselves. The rest of the Intake Dental platform is there if you ever want your calls, forms, and insurance handled too.
Files are end-to-end encrypted: encrypted in your browser before upload, decrypted only by someone holding the link. The key travels in the link fragment, which never reaches our servers. A materially stronger posture than email attachments or consumer file-share tools. As with any transfer tool, share links only with the intended recipient.
Anything a dental workflow produces: DICOM series and zipped CBCT exports, STL/PLY/OBJ scan models, intraoral photos, PDFs, and standard image formats, including files far larger than email's ~25 MB attachment ceiling.
No. They click the link and download in the browser. Accounts are only for senders who want history, expiry control, and download notifications.
The CD drive died a decade ago. A Send link opens on any computer, arrives before the patient does, and shows you it was received.
Yes. When an Intake Dental practice sends from the dashboard, staff can search the patient by name and the send is filed to that patient's chart under Sent imaging, with who received it and whether they opened it. Every practice plan can do this within its 5 free sends a month; Practice Autopilot and AI Dental Office include unlimited patient-linked sending.
See when your files were downloaded. Pair it with Bridge team chat to talk the case through with the receiving office.
A patient asking for their own x-rays, CBCT or chart gets a link in their email and the unlock code by text. Two channels, so one compromised inbox is not enough. No CD to burn, no portal account to create, nothing to install.
Yes. Every package has a "Send files back" button, so a specialist can return a report or post-op scan straight to you, filed in the same case. Returns are free and never count against anyone's monthly sends.
Yes. STL, PLY and OBJ scans open in 3D right in the browser: rotate, zoom and check the margins before importing. The original file downloads untouched for your CAD software.
Yes, and it works exactly like sending to a specialist. You address it to their email, they get the link, and you text them the unlock code separately. They click, they download, and you can see that they did. Patients need no account and nothing installed, which is the whole reason portals go unused.
It is the fastest way we know of. A patient has a right to a copy of their own record, and the usual options are a burned CD, a USB stick, an unencrypted email attachment, or a portal invitation they never finish. Send is a link and a code, it takes about a minute, and the file is encrypted in your browser before it leaves the computer. If your practice is on Intake Dental, the send is filed to that patient’s chart, so months later you can show what you sent and when they opened it.
It is the same mechanism, and the split between the link and the code is what makes it hold up. The file is encrypted before upload and the decryption key rides in the link fragment, which never reaches our servers. The unlock code goes by a different channel, usually text. Someone who gets into the email alone still cannot open the files. Compare that with an attachment, where the inbox IS the key.
Send is free, end-to-end encrypted file transfer built for dentistry: x-rays, CBCT scans, DICOM sets, STL models, case photos. Send to a specialist, a lab, or the patient themselves. The decryption key never touches our servers.
