Yes, a LinkedIn DM can contain video. LinkedIn documents a native video upload in its desktop Messaging composer. Some outreach products put a hosted video link into a message. The recipient may see a preview and opens the video on another site. A campaign that says it 'sends video' may use that second route. Before choosing a tool, identify the object that arrives in the conversation, the account that sends it, and the page where the recipient watches.

01

First identify what the recipient receives

LinkedIn's help page says a member can open a desktop Messaging conversation, use the Picture icon to upload a photo or video, and send it. That establishes a native upload through LinkedIn's own composer. For a campaign, ask the vendor which message types and recipient relationships its video step supports.

Sendspark says its extension inserts a share link in LinkedIn's composer. A recipient can click the preview to watch on a Sendspark page. The vendor also documents mapping a CSV video_link field into compatible outreach messages. Those are vendor-documented workflows. Our review used public documentation.

Sources: LinkedIn: send photos and videos in Messaging, Sendspark: LinkedIn video integration

02

A video campaign does not specify the sending format

HeyReach describes a campaign using Weezly videos and conditional follow-ups. Its guide calls the videos embedded in LinkedIn campaigns, but it does not establish that the campaign uploads a native video file into every recipient's chat. Ask the tool vendor to show the actual sent message, where the video is hosted, and whether that behavior works in the exact message type you will use. Include the recipient relationship and DM, InMail or Sales Navigator format in that demonstration.

The distinction changes the operating decision. A native upload can be enough when a rep is sending a small number of reviewed videos from an eligible conversation. A hosted link can provide a landing page and vendor-side view data. It also asks the recipient to open another site. Sendspark says viewing analytics stay on its platform. Record which system measured a view before using that event to trigger a follow-up.

Sources: HeyReach: video outreach workflow, Sendspark: LinkedIn video integration, LinkedIn: send photos and videos in Messaging

03

Preview behavior can change by recipient

Sendspark says a thumbnail may appear for first-degree connections and recipients who accepted an InMail, while a nonconnection may see no thumbnail in Sales Navigator or Recruiter. It also says LinkedIn caches link previews, so editing a video later may leave the old thumbnail in an already-sent message. Inspect those states on the recipient's screen when evaluating this integration.

A bare link, a thumbnail that opens a hosted page, and a playable file in the conversation are different user experiences. Decide which one the message needs before spending time on personalized thumbnails or campaign logic. Include essential details in accessible text so a recipient can act without opening the video.

Sources: Sendspark: LinkedIn video integration

04

Run a two-account delivery test

Ask a colleague to receive a single harmless test message. Use the intended sender account, relationship, message type and tool plan. Upload a short video through LinkedIn's native composer as the reference. If you accept the vendor workflow's account-policy implications, send one vendor message to the same consenting recipient. Record whether the second message contains a LinkedIn attachment or a URL, whether a preview appears, where playback opens, and whether the vendor's send and view records agree with what the recipient sees. Use this procedure as your team's acceptance test.

If the production campaign uses InMail or Sales Navigator, repeat only that materially different path with another consenting account. Check a nonconnection separately before assuming a thumbnail will render. Do not launch a larger sequence when the recipient cannot open the video, the send state cannot be reconciled, or a missing preview would remove the context the message needs.

  • Record the sender, recipient relationship, message type, video host and expected preview before sending.
  • After delivery, record the visible object, playback destination, accessible text and vendor event record.
  • Hold the campaign if delivery is unclear, the preview is unusable, or the account owner rejects the sending method.

Sources: LinkedIn: send photos and videos in Messaging, Sendspark: LinkedIn video integration

05

Keep platform policy in the purchase decision

LinkedIn says it does not permit third-party software that automates activity on its website, including unauthorized automated messaging, and warns that accounts using such tools can be restricted or shut down. Apply that policy when evaluating vendor video features and desktop extensions, including after a successful delivery test. Decide whether that exposure is acceptable before connecting a campaign tool to a sender account.

For the wider workflow budget, OutreachGenie lists a Free workspace with 80 outreach actions and 500 new prospects a week, plus unlimited visits, lists and flows. LinkedIn restrictions and paid-feature limits still apply. Ask for a recipient-side demonstration of any proposed video workflow before including it in the tool decision.

For a few eligible conversations, a rep can review the recipient and upload the video through LinkedIn's own composer. If a team still evaluates a vendor workflow, require the precise delivery and policy answers above. Require evidence from your own audience before budgeting for a reply-rate lift. The reviewed sources offer no comparable native-file versus hosted-link experiment for that audience.

Sources: LinkedIn: prohibited software and extensions, LinkedIn: send photos and videos in Messaging, OutreachGenie: current pricing

Disclosure: we also make OutreachGenie.