5 client-side LinkedIn tools — all opt-in, all local to your browser.
These tools are off by default. Enable the ones you want in the extension's Options page under LinkedIn Features. Everything runs in your browser — Video Controls Plus never automates LinkedIn actions or sends your data anywhere.
Profile Backup reads the LinkedIn profile page you currently have open and saves a structured copy of it (name, headline, location, About, Experience, Education, Skills, Certifications, and contact info) as a JSON or CSV file you download to your own computer. It is 100% client-side, keeps backups in your browser, and never edits your profile or posts anything on your behalf.
Example: Before rewriting your headline and About section for a job hunt, you back up your current profile to JSON. Two weeks later you back it up again and use the built-in compare to see exactly what changed (headline edited, two new Experience items added).
Does this send my profile data anywhere? No. Extraction happens in your browser, files download straight to your device, and saved backups live in local browser storage. Nothing is uploaded to a server.
Can it back up someone else's profile? It reads whatever profile page is open, but it can only open the Contact info panel on profiles where LinkedIn shows it to you (normally your own). It does not bypass LinkedIn's privacy controls.
What is the difference between JSON and CSV export? JSON preserves the full nested structure (sections, items, media links, contact info) and is best for re-importing or comparing. CSV is a flat Section / Field / Value / Additional Info table that opens cleanly in spreadsheets.
How many backups are kept? Up to 10 versions per profile by default. Older ones are dropped automatically, and you can delete or clear them yourself at any time.
Does it automatically back up on a schedule? There is an optional auto-backup interval (daily/weekly/monthly), but it is OFF by default. You turn it on yourself if you want it.
It only reads the profile page that is open in your tab and only the sections it can find in the page DOM; if you skip the Contact info step or LinkedIn restricts it, email/phone may be blank. Saved backups are capped at 10 versions per profile and live only in this browser — they are never uploaded anywhere. LinkedIn changes its page layout often, so some fields may occasionally come through empty.
Post Archive scrolls the LinkedIn page you currently have open to collect your posts and saves them — text, engagement counts (likes/comments/shares), hashtags, mentions, media references, and post type — into named, searchable archives stored in your browser. You can then export an archive to PDF, HTML, or JSON. It only reads what is on the page and never posts, deletes, or edits anything.
Example: You want a record of a year of posting before you go quiet for a while. You scroll-collect your posts into an archive called '2025 Posts', then export it to HTML so you have a self-contained file showing each post with its like/comment counts and hashtags.
Where are my archived posts stored? In your browser's local extension storage. Exports download to your device. Nothing is sent to any server.
Will it capture every post I have ever made? No. It can only read posts that load as you scroll the current page. Posts that LinkedIn never renders in the feed/profile won't be included.
Are the like and comment numbers live? No — they are a snapshot captured at the moment you archive. Re-archive later if you want updated counts.
Can I search across multiple archives at once? Yes. Search and filters run across all archives you have saved, ranking matches by relevance and highlighting where the term appears.
Does archiving change anything on LinkedIn? No. It is read-only — it scrolls and reads the page. It never edits, deletes, reposts, or publishes anything.
It can only archive posts that actually render on the page you scroll — it does not have a private API into LinkedIn, so very old posts that never load won't be captured. Engagement counts are read from the page text at archive time and are a snapshot, not live numbers. Archives stay in this browser only; LinkedIn layout changes can affect what gets captured.
Connection Exporter reads your LinkedIn connections list (you must be on the connections page) and lets you export it to CSV or JSON with the fields you choose — name, headline, parsed company and position, location, profile URL, connection date, mutual count, plus any tags and notes you added yourself. It is entirely client-side, organizes data only, and never sends connection requests or messages.
Example: You want a CRM-style list of your network. You collect your connections, tag a batch as 'warm-lead' and 'ex-colleague', then export a CSV with Name, Company, Position, Profile URL, and your Tags columns to import into your own spreadsheet.
Does this scrape LinkedIn or break their rules? It only reads the connections page you have open as you scroll it, in your own browser — it does not mass-scrape or automate anything. It organizes data you can already see and never sends requests or messages.
Are emails and phone numbers exported? No. The connections list view doesn't expose those, so the export covers name, headline, parsed company/position, location, profile URL, mutual count, and your own tags/notes.
Why is the company or position sometimes wrong? Those are inferred from the headline text by splitting on 'at' or '-'. Unconventional headlines can parse imperfectly; you can correct them in the exported file.
Does the Google Sheets option upload my data to Google? No. It just formats your connections into a headers-and-rows table that you copy and paste into a sheet yourself. The extension does not call any Google API or send your data anywhere.
Where are my tags and notes saved? Locally in your browser, keyed per connection. They are included in exports if you enable those fields, but they never leave your device on their own.
Company and position are parsed heuristically from each connection's headline (splitting on 'at' or '-'), so they can be imperfect when a headline is unusual. It only reads connection cards that load as you scroll the connections page, and email/phone are not pulled from the list view. All data and your tags/notes stay in this browser; nothing is uploaded.
Message Exporter reads a LinkedIn conversation you have open in the Messaging page and saves it as a readable PDF, HTML, plain-text, or JSON file, with senders, timestamps, attachment references, and optional grouping by date. It is fully client-side, read-only, and never sends, deletes, or replies to any messages.
Example: A client agreed to project terms over LinkedIn messages. You open that conversation and export it to PDF so you have a clean, dated transcript for your records alongside the rest of the contract paperwork.
Are my private messages uploaded anywhere? No. The conversation is read in your browser, exported to a file on your device, and cached only in local extension storage for search. Nothing is sent to a server.
Does it download attachments? No. Attachments are referenced by name and link in the export (e.g. [file: contract.pdf]); the files themselves are not downloaded.
Can it export a conversation I haven't opened? No. You must open the thread in LinkedIn Messaging; the tool then scrolls and reads that open conversation only.
Will exporting mark messages as read or notify the other person? Selecting a conversation opens it the same way clicking it would, which can mark it read on LinkedIn's side, but the tool never sends, replies to, or deletes anything.
Which format should I use for a legal/record copy? PDF or HTML give a clean, formatted transcript with senders and dates; JSON is best if you need the raw structured data.
It only reads the conversation currently open in your Messaging page; it cannot pull a thread without you opening it. Attachments are referenced by name/link, not downloaded as files. Older messages are captured only if they load when the thread is scrolled. Everything stays in your browser, and LinkedIn DOM changes can affect capture.
Job History Export is a local job-application tracker and exporter: you log applications (title, company, location, status, notes, interview stages) and it keeps a status-change timeline, computes response/interview/offer rates, and exports everything to CSV, PDF, or JSON. It can also read LinkedIn's 'Applied jobs' page to pre-fill entries. It stores data only in your browser and never submits or withdraws applications for you.
Example: During a job search you track 40 applications. As replies come in you bump statuses, and the dashboard shows a 35% response rate and 12% interview rate. Before a check-in with a mentor you export a PDF report with the timeline of each application.
Does this apply to jobs or message recruiters for me? No. It is a tracker and exporter only. You log and update entries; it never submits applications, withdraws them, or contacts anyone.
How are the response and interview rates calculated? They are derived from the statuses you record — e.g. response rate counts applications that moved beyond 'applied'. They reflect your tracked data, not any private LinkedIn metric.
Where is my application data stored? Entirely in your browser's local extension storage. Exports download to your device. Nothing is uploaded to a server.
What does the 'Applied jobs' import do? When you are on LinkedIn's Applied jobs page, it reads the visible job cards and creates 'applied' entries for ones you don't already have, so you don't re-type them. You then maintain statuses yourself.
Can I include notes and interviews in the export? Yes. Settings let you include notes, interview stages, and the full status timeline in CSV/PDF/JSON exports, and choose sort order and date format.
Statistics like response, interview, and offer rate are computed from the statuses you record — they are only as accurate as the data you keep up to date. The 'Applied jobs' scrape only reads what loads on that LinkedIn page and seeds entries as 'applied'; it does not pull full status history. It never applies to, or withdraws from, jobs on your behalf. All data lives in this browser only.
All features
Last updated 2026-11-10 by the Video Controls Plus team.