DEV Community: Remove AI Meta

The LinkedIn CR icon is a manifest, not a sticker

Remove AI Meta — Mon, 28 Sep 2026 08:57:49 +0000

LinkedIn's Content Credentials icon is a decision the site made after it received the file. It is not a sticker baked into the pixels, and deleting "the icon" from a screenshot does nothing to the next upload.

I separate three objects before I touch the file.

The manifest in the file is a signed note. It can say a camera captured the picture, an editor changed it, or a generative tool created part of it. On a JPEG that note is usually an APP11 segment using JUMBF, sometimes with an XMP pointer. On a PNG it is a caBX chunk. On a WebP it is a C2PA-style RIFF chunk. Content Credentials is the name on that pin. C2PA is the spec for the signed manifest. This is the only one of the three that a metadata cleaner can see and remove.

The cloud record is a copy a publisher stored somewhere else. Photoshop can attach credentials to the file, publish them, or do both. Stripping your JPEG does not log into that service, and it does not delete the cloud copy.

The platform label is LinkedIn's CR icon, or Instagram's AI info chip, after the upload. If the icon appeared because the manifest was still in the file, a new upload of a cleaned file can go up without it. The live post keeps the decision LinkedIn already stored. Another signal, including a pixel watermark, can still produce a label on the new upload.

To clear the manifest from the copy I am about to publish:

Drop the JPEG, PNG, or WebP I will actually upload. A sample only shows the report.
Set the mode to AI provenance, so the pass targets the C2PA manifest and related AI metadata and leaves ordinary camera EXIF alone.
Clean and verify. The After column has to be a new scan. I download only if the C2PA chip cleared. The name ends in -cleaned.
Upload that download. The file next to it still has the old manifest, which is how the CR icon comes back.

Empty is a real result. If inspect shows no C2PA chip, this file does not contain a manifest the scanner recognizes, and cleaning it again will not remove a label LinkedIn attached for another reason. AI provenance also leaves GPS in place on purpose. A delivery set that must drop the map pin needs the privacy pass, not this one.

SynthID and TrustMark stay in the pixels. A clean After report is not a watermark-verifier result.

The three-way split, and what a strip does not change on a live LinkedIn post, is the map of those three objects.

Quarter-turns for a Litematica placement

Remove AI Meta — Mon, 28 Sep 2026 08:57:33 +0000

Turning the downloaded file around does not turn the house. A structure block cannot read a .litematic, and renaming it does not spin the door. WorldEdit //rotate edits a .schem clipboard, not this hologram.

Litematica stores the turn on the placement: an origin, a rotation, a mirror, and a Locked flag. The file you generated stays as it was. Quarter turns only. There is no 15 or 45 degree step.

Load the .litematic and create a placement so the hologram is actually in this world. If you cannot see it, fix rendering before you edit an origin you cannot see. All-rendering off (M + R) also makes the nudge scroll do nothing.
Open Schematic Placements with M, then Schematic Placements, or press M + P. Click the row until it has the white selection outline. Middle-click the ghost in the world does the same select, while Schematic Placement mode is active and you are holding the tool item. The default tool item is a stick.
Press Numpad Minus, or click Configure. The screen title is Configure Schematic placement. Numpad Multiply is the Area Editor, which is a different screen. On a laptop the numpad keys are often a number row, so bind openGuiPlacementSettings if Minus does nothing.
Click Rotation. Each click is 90 degrees clockwise. The action bar should say the placement rotated. Click Mirror if the build needs a flip. Mirror does not change the palette.
To slide it, hold the stick in Schematic Placement mode, hold Left Alt, and scroll. It moves one block along the direction you are looking, including up and down. Left Alt in Area Selection mode nudges the box instead of the house. Switch modes before you scroll. Type the origin when a scroll would walk the build through a wall. Files from the browser compiler put the region at 0, 0, 0, so the floor is the minimum corner.
Set Locked once the ghost sits where you want it, so a later scroll does not shove the origin. A locked placement tells you it cannot be modified. Unlock before the next edit. Removing a locked placement asks you to hold Shift.

House and castle doors on these files sit on the low-Z face. Keep clicking Rotation until that face meets the path. You cannot rotate the roof alone. Builds from this compiler are one region. Sub-region rotation exists in the mod if you add regions later. It is not a second file.

Paste Schematic in world is creative-only. Survival still builds from the hologram.

The button labels, the unbound rotate hotkey, and the Locked flag are written up as the placement configure steps.

Paste one ChatGPT answer and check the table before you download

Remove AI Meta — Mon, 28 Sep 2026 08:51:09 +0000

The brittle part of "ChatGPT to Word" is not the heading. It is the pipe table. Copy a long answer, paste it into Word, and the table is still a row of | characters with a separator line under the header. Lists sometimes survive. Tables, fenced code, and a Mermaid block usually do not.

I only do this when I already have one answer copied. A full multi-turn archive is a different tool. ChatGPT also does not offer a reliable Export to Word button. Some chats can emit a file through the file tool, and that link expires or drops the table. For one polished answer I copy the Markdown and convert it locally.

On the ChatGPT message, use Copy, not a drag-select that grabs the rendered HTML. Copy keeps the Markdown, which is what the converter needs.
Paste into the preview. Headings should become heading styles, not leftover # marks. A GFM pipe table should become a real table, including the column alignment. A fenced code block should stay monospace, with the language label if one was there.
Look at math and diagrams before downloading. Inline LaTeX should become an editable equation. A mermaid fence should become a diagram image. If the diagram fails to render, the source fence should remain with a note, not disappear.
Download the .docx if I need a file. Copy formatted if I am pasting into a document I already have open. Nothing in that conversion is uploaded.

Before I send the file I read it once for secrets. An export does not know which paragraph was an API key.

I check the table in the Markdown-to-Word preview before I download. One answer stays on the free converter. A folder of Markdown files is the paid batch, and I do not need it for a single reply.

A WebVTT file is not a Word script until the cues collapse

Remove AI Meta — Mon, 28 Sep 2026 08:50:08 +0000

Opening a .vtt in Word feels like it should be enough. Word will open it. You then still have cue numbers, --> timing lines, and NOTE or STYLE blocks sitting in the middle of the dialogue. That is not a script anyone wants to comment on.

WebVTT is a little worse than SubRip for this job because the useful speaker data is often a tag, not a line of text. A cue can carry a <v Speaker> voice span. Consecutive cues from the same speaker should become one paragraph. A raw paste keeps every cue as its own broken sentence.

I convert in the browser, with timestamps as a choice rather than a leftover.

Export the captions as .vtt from the tool that made them (YouTube Studio, Zoom's VTT download, a caption editor). UTF-8 is the encoding I want. If the file is a .srt, the same converter reads that too, but the voice-tag case is the VTT one.
Drop the file, or paste the cue text. Parsing stays on the machine. The captions are not uploaded to build the document.
Decide whether the Word file is a review copy or a reading script. Leave timestamps on for a translator, a QA pass, or anything that has to point back at the video. Turn them off for minutes or a client-facing read. The preview updates before download, so I check the first speaker change and the last cue there.
Download the .docx. It opens in Word, Word Online, and LibreOffice. Copy formatted is the alternative when I want the preview on the clipboard instead of a new file.

What flattens: karaoke timing, drawings, and font effects become plain timed text. What should survive: speaker labels from [Name], Name:, and those WebVTT voice tags, merged when the same person continues.

I do this with the subtitle-to-Word converter. One file stays free. A folder of caption files is a separate unlock and is not required for a single WebVTT.

Clean a JPEG in the tab you already have open

Remove AI Meta — Mon, 28 Sep 2026 08:49:55 +0000

An AI metadata remover is a file cleaner, not a promise that a platform will stop calling the picture AI. The tags people actually need gone are ordinary and specific: GPS and camera EXIF, a C2PA Content Credentials manifest, and generator notes in XMP or IPTC. A pixel watermark such as SynthID is a different object, and this pass does not touch it.

I clean one JPEG, PNG, or WebP in the tab I already have open. HEIC is not ready for that path, so I export to one of those three first. PDF and video are out of scope too.

Drop the file you will publish. The sample image only shows what a report looks like.
Pick the mode for the job. AI provenance removes the C2PA / JUMBF manifest, Content Credentials XMP, and known AI tags, and it leaves ordinary camera EXIF on purpose, including a map pin. Privacy EXIF is the pass when that location cannot go to a client. Strip all clears every category the report listed.
Press Clean and verify. The After column is a fresh scan of the cleaned bytes, not a duplicate of the Before list. If a C2PA chip is still there, do not download yet.
Download the file whose name ends in -cleaned, and send that file. The original is still sitting next to it.

The picture itself stays. Metadata segments come off, the image is not recompressed, and the dimensions do not change. Inspect, clean, and verify stay in the browser. The photo is not uploaded to produce the cleaned file.

A clean After report still does not do three things I used to assume it did. It does not delete a cloud copy of the credential that Photoshop or another publisher stored elsewhere. It does not edit an Instagram, Facebook, or LinkedIn post that already ingested the old file. And it does not stop a platform from labeling a new upload because of a signal that was never in the metadata.

I run that check in the in-browser cleaner. One image is free. A folder comes back as a single ZIP only after the unlock, and the same limits apply to every file in the set.

The clipboard test for an Instagram Reel link

Remove AI Meta — Mon, 28 Sep 2026 08:49:13 +0000

People who need a copy of an Instagram link usually already have the Reel on screen. The share sheet still hands them the wrong object: a profile, a Story, an Explore grid, or a /share/ blob that never resolves.

I use one clipboard test before I paste anything into a song finder.

Open the single Reel. On a phone it should fill the screen. Progress bars across the top mean you are on a Story, and a Story does not have a stable public Reel URL. A profile grid is not a link yet. Tap the clip first.

On someone else's Reel, tap the paper plane. Copy link (sometimes labeled only Link) sits with the round icons, not inside a row of people named Send to. On a current iPhone that icon is often past the right edge. Swipe the icon row before you decide the button is gone. Tapping a person sends a DM. That is not a copy. If the plane is missing, the same command is under the three-dot menu.

On your own Reel, Instagram usually hides the share-to-copy path. Tap the three dots, then Link. The clipboard result has the same shape.

Paste into Notes and read it.

Pass: https://www.instagram.com/reel/… or /reels/…, then a short code of letters and numbers. A ?igsh= tail can stay.
Fail: only a username, an Explore URL, or a /share/ string with no short code you can point at.

A /share/ link can still be useful. Open it once in a normal browser, wait until the address bar changes to /reel/ plus the code, and copy that second URL. Pasting the unresolved blob is the usual desktop failure.

Android is the same job with a different sheet. Copy link may sit under More, and some builds say Copy URL. Long-pressing the video often opens playback speed, not the address. Dismiss that and use the plane or the three dots.

On a computer, use a normal browser window, not only a logged-in embed. Select the full URL, including https://, once the bar shows /reel/ or /reels/ and the short code. A bar that stops at the username is the profile. Click the clip in the grid first.

An iMessage preview is not the URL either. The bubble can say Instagram and still hide the address. Press and hold for Copy, or open it until Safari's bar shows /reel/, then copy from Safari.

Copying a public Reel link does not notify the creator the way a like does. A private account or a Close Friends clip can still land a URL on your clipboard, and a public finder cannot fetch that audio.

Phone, Android, and desktop branches, including the share-blob case, are in the Reel-link checklist. When the clipboard passes, paste that same URL into the finder.

A Directory of Browser Tools Grouped by the Job, Not the Hype

Remove AI Meta — Tue, 22 Sep 2026 08:37:33 +0000

Most tool lists are SEO piles. I needed a directory grouped by job: converters, generators, editors, calculators. That is Web Tools List.

Search the job, not the brand. A useful tool works in the browser and explains the output.

Browse webtoolslist.com by category. The useful web is still small pages that do one thing.

Play a Browser Mech Game, Then Browse More Robot Wars

Remove AI Meta — Tue, 22 Sep 2026 08:37:28 +0000

I wanted a mech fight that loads in a tab: no launcher, no account wall before the first match. Mechangelion is that page, plus a directory of robot, tank, and stickman war games nearby.

A 2-minute session should not require a 4 GB install. Readable hit feedback and a round that ends matter more than a long HP sponge.

Start at mechangelion.com. Play, then browse.

Find the Song Used in an Instagram Reel Without Guessing

Remove AI Meta — Tue, 22 Sep 2026 08:32:07 +0000

Reels hide the track behind a sticker and a truncated title. If you are clearing music or matching a reference, guessing from a 3-second hook wastes an afternoon.

Reel Song Finder is the page I open when I need the track name from a Reel.

Read the sound label, search with the share URL, confirm with a 10-second listen. Editors get a title and artist.

The tool is at reelsongfinder.com.

Export a ChatGPT Thread to Word Without Losing the Structure

Remove AI Meta — Tue, 22 Sep 2026 08:32:03 +0000

ChatGPT is fine for drafting and painful for filing. Copy-paste into Word drops code fences, turns lists into a wall, and loses who said what.

I use ChatGPT to Word when a thread has to become a note, a brief, or an appendix.

Headings, lists, code blocks, and user vs assistant turns should survive. Export once, then edit in Word.

The exporter is chatgpt2word.com. Treat the chat as a whiteboard. Treat Word as the artifact.

Turn SRT Subtitles Into an Editable Word Document

Remove AI Meta — Tue, 22 Sep 2026 08:26:42 +0000

SRT files are great for players and terrible for editors who live in Word. Timecodes, blank lines, and cue numbers get in the way of a script pass.

I convert them with SRT to Word when I need comments, highlights, or a bilingual table.

A producer needs readable paragraphs, not cue indexes. Translators get a .docx. I keep the SRT as the source of truth for timing.

The converter is at srt2word.com. Upload, download Word, send to review.

Strip C2PA and IPTC Metadata From AI Images Before You Publish

Remove AI Meta — Tue, 22 Sep 2026 08:26:37 +0000

AI image tools now stamp Content Credentials and older IPTC fields into files. That can be useful for provenance. It is a problem when you need a clean asset for a client who does not want model traces in the bytes.

I keep a dedicated inspector for this: Remove AI Meta.

What is actually in the file

Typical extras include C2PA manifests, IPTC software fields, and EXIF that still names the generator. Viewing the image is not the same as reading those chunks.

A publish checklist

Inspect the download
Strip credentials if the brief requires a clean file
Re-inspect so you did not leave a second packet
Keep the original if you still need provenance later

The before-and-after flow is on removeaimeta.com. Metadata is not the image. Treat it as a separate document attached to the pixels.