How to Remove a Mugshot From the Internet and Google (2026)

To remove a mugshot from the internet, you work two fronts at once: get the image taken down at the source (every site hosting it) and get it de-indexed from search so it stops appearing when someone looks up your name. There is rarely one button that erases a mugshot everywhere, because the underlying arrest record is usually a public record. But most people can meaningfully reduce or eliminate a mugshot's visibility by combining source removal across the publishing ecosystem, search engine removal policies, and, where eligible, expungement or record sealing. This guide covers both halves: the ecosystem (how mugshots spread, who profits, which levers actually move them, and what is realistically removable) and the Google-specific steps for clearing the search result. Here is the ecosystem first: how mugshots spread, who profits, which levers actually move them, and what is realistically removable.

How one arrest becomes dozens of listings

A mugshot begins as a public record. When someone is booked, the arresting agency (a county sheriff or a police department) frequently publishes the booking photo and arrest details as part of the public record, which is legal and, in many jurisdictions, automatic. What happens next is the real problem. A category of commercial mugshot sites scrapes those county and state booking feeds in bulk, on a rolling basis, and republishes them, engineered to rank for your name in search. Because these platforms aggregate thousands of names and are built for search visibility, a single arrest photo can land on a dozen different sites within weeks. Sites commonly named in this space include Mugshots.com, Arrests.org, BustedNewspaper.com, JailBase.com, and a rotating cast of clones and regional imitators, many of which share the same underlying data pipes.

That shared plumbing is why removing the image from one site rarely solves anything. The same booking feed that fed site A also fed sites B and C, so a listing you clear from one aggregator can reappear on a sibling site weeks later. It is also why a charge that was dropped, dismissed, or never even led to a conviction can follow someone for years, surfacing in front of employers, landlords, lenders, and dates who run a quick search. The record being public does not obligate the internet to keep amplifying it, and amplification, not the record itself, is what you are actually fighting.

The pay-to-remove trap, and why you should almost never pay

Many mugshot sites run a deliberate business model: publish the photo for free, then route you to a removal service and charge a fee to take it down. As reporting and litigation have documented, the same entity often owns both the publishing site and the removal service, so the mugshot itself is essentially an advertisement for the far more lucrative takedown business. Some operators run networks where paying one site simply causes the image to reappear on a sister site, so you pay again. This is not customer service. It is closer to extortion, and paying often makes things worse by signaling that your name is worth targeting.

The trap is not hypothetical. In one of the highest-profile cases, California prosecutors charged the operators behind Mugshots.com with extortion, identity theft, and money laundering; the case resolved in 2025 with the defendants pleading no contest and being ordered to pay restitution. The lesson for you is practical: a site demanding a fee to remove a public booking photo is a red flag, not a customer-service desk. Before you spend a dollar, assume there is a free or legal path, because in most cases there is. Professional mugshot removal is built specifically around getting these images down without feeding the fee, using policy, law, and documentation instead of the operator's own payment funnel.

The crackdown: payment processors, prosecutors, and Google

You are not fighting this alone or without allies, because the ecosystem has been squeezed from three directions. First, payment processors. After a widely cited 2013 investigation, American Express, Visa, Mastercard, Discover, and PayPal moved to stop processing payments to mugshot sites and their removal services, cutting off the money at its source and doing more damage to the model than early legislation did. Second, prosecutors and state attorneys general have brought criminal and civil actions against the worst operators, the Mugshots.com case being the marquee example.

Third, and most useful to you day to day, Google. Google built ranking signals that demote known mugshot-extortion sites, an effort that traces back to a 2013 algorithm change, and it later added a dedicated removal path for content on sites with exploitative removal practices, meaning sites that charge people to take down personal information. Google's own policy also states that when it processes a high volume of personal-information removals involving such a site, it demotes the rest of that site's content and looks for the same pattern across related sites. The strategic takeaway is almost poetic: the sites shaking you down are frequently the exact sites search engines are most willing to help you bury. That reshapes the whole plan, because it means the extortion fee is rarely the path, and the free de-indexing route is often the stronger one.

State anti-mugshot laws: a real lever, with limits

Over the past decade, more than a dozen states have passed laws aimed squarely at the pay-to-remove business. The details vary, but they generally do one of two things: prohibit sites from soliciting or accepting a fee to remove, correct, or modify booking-photo information, or require removal under certain conditions, such as when charges are dropped, dismissed, or the person is acquitted. California, Georgia, Illinois, Texas, Colorado, Florida, Oregon, Utah, and others have enacted versions of these statutes. California's law, for instance, bars a publisher of criminal-record information from charging a fee to take it down; Texas tightened its rules further in recent legislation restricting how booking photos are released and used.

Two honest caveats. First, enforcement is uneven. Many of these laws lack strong enforcement mechanisms, and offshore or anonymous operators are hard to reach, so the statutes have been only partly effective in practice. Second, they are a lever, not a guarantee. A well-drafted removal request that cites the specific statute in your state, and attaches proof that you qualify (a dismissal, an acquittal, or an expungement), carries real weight and gives you a basis for escalation to your state attorney general if the site refuses. But you should treat the law as ammunition for a documented request, not as a magic phrase that forces instant compliance. Where a booking photo overlaps with a formal court record, this work often runs alongside court record removal, since clearing the record strengthens both.

Step one: map the full footprint before you touch anything

The single most common self-removal mistake is playing whack-a-mole: finding one listing, firing off a removal request, and declaring victory while five more copies keep ranking. Because mugshot sites share booking feeds, you have to inventory every copy first. Search your full name, your name plus your city or county, and your name plus words like arrest or booking, and record the exact URL of every page displaying the image, along with which site hosts it and whether it offers an opt-out or demands a fee. Note image-search results separately, since a photo can persist in image search even after the page text changes.

This inventory is not busywork. It tells you which listings have a free opt-out, which are covered by your state's law, which are on sites Google will de-index as exploitative, and which are on legitimate news outlets that will be much harder to move. It also lets you sequence the work so you are not accidentally re-crawling and refreshing a page (which can temporarily boost its ranking) before you are ready to address it. A structured footprint map is the foundation of any serious effort, and it is the first thing a professional content removal engagement produces before sending a single request.

How legitimate source removal works, site by site

Once you have the map, source removal proceeds one platform at a time, matched to that site's actual process. There are a few clean bases for a request. Legal status: if your charges were dropped, dismissed, or you were acquitted, or if you were a minor at the time, many sites (and several state laws) require or invite removal on that basis. A cleared record: an expungement or sealing order is the strongest documentation you can attach. A factual error: an incorrect name, wrong charge, or mismatched photo is both removable and, if published as fact, potentially defamatory. A genuine privacy or safety risk: some platforms will act when publication creates a real-world danger.

The discipline that makes it work is precision and restraint. Submit a formal, documented request that cites the specific basis and attaches the paperwork, rather than a vague plea to "please take this down." Do not use a site's generic opt-out form without your documentation ready, and do not pay the fee to jump the line. If a site ignores a documented, law-backed request, escalation is available: a cease-and-desist, a complaint to your state attorney general where fee practices are restricted, and, for false content, a defamation posture. The goal throughout is to get the image down using leverage the operator cannot monetize, so you are not funding the next round of extortion.

Expungement and sealing: the most durable fix

The most durable solution addresses the record itself. If your charge was dismissed or you are otherwise eligible, expungement (which erases or destroys the record) or sealing (which restricts public access to it) through the court removes or limits the underlying public record. Once that record is cleared, republishing it becomes far weaker ground for any site to stand on, and your removal and de-indexing requests gain real force. Eligibility and process vary sharply by state and by the nature of the charge, and the paperwork matters, so this is worth confirming with a local attorney.

Sealing and expungement are slow, often measured in months, and they do not automatically reach out to every website displaying the record. You still have to enforce the order site by site, sending it to each republisher and then clearing the lingering search results afterward. But nothing else produces as clean an outcome, which is why, for eligible cases, it is worth starting the court process early and running the faster removal and de-indexing levers in parallel rather than waiting.

De-indexing from search, so the copies stop surfacing

Even when a page cannot be deleted, getting it out of search is often the outcome that matters most, because a result that does not appear in a name search has little real-world impact. Mugshot content sits squarely inside search engines' removal frameworks: Google will consider removing pages from sites with exploitative removal practices and also removes certain personal and sensitive information on request. Success depends on documenting each page precisely and matching it to the correct policy basis, not filing a vague complaint. After a source page actually comes down, a final cleanup step, Google's tool to refresh outdated content, clears the stale result faster than waiting for the normal re-crawl.

Because the search-engine mechanics (which policy fits, how to file each request, how to avoid triggering a counterproductive re-crawl, and what timelines to expect) have their own detail and their own pitfalls, we cover them separately and thoroughly in the companion guide to removing a mugshot from Google. Treat de-indexing as the partner to source removal: source removal takes the image off the page, and de-indexing makes sure the page and its cached copies stop appearing while you clean up the rest.

What is realistic, and what is not removable

Honesty here saves you money and heartbreak. The strongest cases are older records, dropped or dismissed charges, records that have been sealed or expunged, and images republished by commercial mugshot sites rather than by the press. Those are the situations where source removal, state law, and de-indexing combine to actually move the needle. The hardest cases are the opposite: a recent or active arrest with no legal change, and genuine news coverage by a legitimate outlet reporting on a matter of public interest. News reporting is generally protected, and no reputable provider can force a newsroom to unpublish lawful journalism.

When a mugshot appears in legitimate, lawful coverage that cannot be removed, the honest strategy shifts to suppression: building and strengthening accurate, authoritative content about you so it ranks above the coverage and pushes it off the first page, where most searchers stop looking. Suppression deletes nothing and is not instant, but for content that is here to stay it is often the only thing that changes what people actually find. It pairs naturally with the removal work on the copies that can come down. You can read more about how suppressing negative search results works as the realistic path when removal is off the table. And be wary of anyone promising to erase every trace of a mugshot overnight or guaranteeing a result: removal is outcome-dependent, and guarantees are the surest sign of a scam.

Part two: getting the mugshot out of Google, step by step

Source removal and search removal are separate jobs, and for most people the Google result is the one that matters, because it is what an employer, landlord, or date actually sees. The sections below walk through the Google side in detail: what Google will and will not remove, the free exploitative-practices request, image results, the Results about you tool, and what to do when removal is not possible.

The record, the source page, and the Google result are three different things

Most failed mugshot-removal attempts come from blurring three separate things. The arrest record is the public booking data held by a sheriff or police department. The source page is a commercial site like Mugshots.com or a BustedNewspaper property that scraped that record and republished it to rank for your name. The Google result is the link, title, snippet, and thumbnail that appears in search when someone looks you up. This guide is about that third thing. De-indexing removes the Google result without necessarily deleting the source page or the record, and for reputation purposes that is often enough: if the listing does not appear when an employer, landlord, or date searches your name, its real-world impact drops sharply. Understanding which layer you are actually fighting tells you which lever to pull, and it is why a vague request to Google to "take down my mugshot" so often goes nowhere while a precise, policy-matched request succeeds.

What Google will actually remove from search

Google removes results in two broad ways, and it helps to know which bucket your situation falls into before you file anything. The first is policy-based removal, where a page violates one of Google's published removal policies. For mugshots, the two policies that matter most are its personal-information policy and its dedicated exploitative-removal-practices policy (covered in the next sections). The second is legal removal, where content is unlawful, for example a page you have a valid court order against, or a listing that survives only because of an expunged or sealed record. Google's personal information removal policy covers exposed data that enables real harm: your home address, phone number, or email, government ID numbers, bank or credit-card numbers, images of your signature or ID, confidential login credentials, and certain medical records. What Google generally will not remove on a simple privacy request is a result that merely points to an official government or public record, or content it considers genuinely newsworthy. That is not a reason to give up, it is a reason to file under the right policy, because mugshot sites usually fall under the exploitative-practices path rather than the government-record exception.

Google demotes and de-indexes the pay-to-remove mugshot sites

This is the single most important thing to understand about removing a mugshot from Google specifically. Years ago Google recognized that a whole category of sites exists to publish arrest photos and then charge frightened people to take them down, and it built its algorithm to demote those sites so they rank lower for personal-name searches. Then it went further and created a dedicated removal path. Google's policy on content on sites with exploitative removal practices lets you ask Google to remove a page from search results when the site requires payment to the site or a third party to have the content taken down. In plain terms: the mugshot sites shaking you down for a fee are the exact sites Google is most willing to de-index for free. To qualify, three things must be true: you must be the subject of the content (or an authorized representative), the site must require payment to remove the content, and the site cannot be a genuine business-review site (this policy is not a backdoor to scrub Yelp). Google is explicit that when it approves the request the reported URL will no longer appear in Google Search, though the content may still exist on the web and be reachable by direct link, social media, or another search engine. That is exactly the point of this guide: you are removing the Google result, which is what nearly everyone actually sees.

How to file the exploitative-removal request

The mechanics are free and do not require a lawyer, though precision is what separates approvals from rejections. First, build a clean inventory of the exact URLs you want removed. Search your name, your name plus your city, and your name plus "mugshot" or "arrest," and copy the full URL of each offending result rather than just the homepage of the site. For each one, capture the direct link to the specific page, and, if the photo appears in image search, the image URL too. Then file through Google's exploitative-removal-practices form, selecting the option that the site charges a fee to remove content, and paste in each URL. Document, briefly and factually, that the site demands payment for removal. Submit one clean, well-documented request rather than a flood of vague duplicates, which can slow legitimate reviews. Expect a decision in a window of days to a few weeks, and be prepared to supply additional URLs as you find more copies, because the same booking photo is often syndicated across several sites at once. If you would rather not manage the URL mapping and per-page documentation yourself, that coordination is the core of professional mugshot removal.

Removing the mugshot from Google Images

A mugshot in Google Images is its own problem, because the thumbnail can keep surfacing in the image tab and in name searches even after the web result is handled. The key fact is that Google indexes the image from the page that hosts it. When you file a removal request, treat the image as a distinct target: capture both the URL of the image itself (right-click the result and copy the image address) and the URL of the page it sits on, and include both. The exploitative-removal and personal-information paths both accept image URLs. If the source page has already been taken down or the photo swapped out but the old thumbnail still appears, that is a caching issue rather than a policy issue, and the Refresh Outdated Content tool (below) is the right fix. The practical rule: never assume that clearing the web result automatically clears the image, and never assume clearing the image is done until you have checked the image tab directly for your name.

The Results about you tool and personal-information removals

Google's Results about you tool is built for exactly this kind of exposure. It lets you find results in Google Search that show your personal contact information, request their removal, and, importantly, monitor your name so Google notifies you by email when new matching results appear. For mugshots specifically, the tool is most useful when the listing also exposes personal identifiers, your home address, phone number, or a government ID number alongside the booking photo, which many aggregator pages do. Those identifiers give you a clean personal-information basis for removal under Google's personal-information policy, separate from the exploitative-practices angle, and it is often worth filing on both grounds where they apply. The monitoring feature matters because mugshot sites share data feeds, so a listing you clear from one site can resurface on a sister site later. Turning on notifications means you learn about the new copy from Google rather than from a job interview that went sideways. Note that some Results about you features roll out by region and are limited to users over 18.

Refresh Outdated Content: the closing step after a source removal

Getting the source page taken down does not instantly clear Google. Google caches pages, so a stale result and its old thumbnail can linger for days, weeks, or occasionally months until Google re-crawls on its own schedule. That is what Google's Refresh Outdated Content tool is for. Once the source page genuinely returns a 404 or 410 (page gone) or the specific mugshot content has actually been removed from the live page, you submit the URL and Google re-crawls it and clears the outdated result faster. The discipline here is timing: this is a closing move, not an opening one. The tool only works when the underlying page has truly changed, so submitting it before the source has removed the photo does nothing and wastes the request. Verify the page or image is actually gone first, then refresh. This is also why filing a removal form on a live, unchanged mugshot page under the wrong tool backfires, an ill-timed submission can even prompt a re-crawl that refreshes the listing's timestamp. Sequence matters as much as the request itself.

When Google removal is not possible: suppressing the result

Sometimes the Google result cannot be removed at all. If the arrest is recent, the case is active, or the mugshot appears in legitimate news coverage of a matter of public interest, Google's policies generally will not de-index it, and news reporting in particular is protected. In those situations the honest strategy is suppression: publishing and strengthening accurate, authoritative content about you (an optimized personal or professional site, well-maintained profiles on platforms Google trusts, credible third-party coverage) so that it ranks above the mugshot result and pushes it off page one, where the overwhelming majority of searchers never venture. Suppression does not delete anything and it is not instant, typically a multi-month effort, but for a result that is here to stay it is often the only thing that meaningfully changes what people see when they search your name. This is the discipline behind suppressing negative search results, and it pairs naturally with any removal work already underway. It is also the realistic alternative to the fantasy that everything can be erased overnight.

The bottom line

A mugshot can feel like it lasts forever, but its visibility usually does not. The record may be public, yet the sites amplifying it are frequently the very ones payment processors cut off, prosecutors have charged, and search engines are willing to demote, and the extortion fee is rarely the answer. Map the full footprint, remove at the source using legal status and documented requests, use your state's anti-mugshot law as leverage, clear the underlying record through expungement or sealing where you are eligible, de-index the results that remain, and suppress only what genuinely cannot be removed. Since 2013, Reputation Resolutions has handled more than 5,000 engagements across 40-plus countries, and we will tell you plainly what is removable in your specific situation before you spend a dollar. If a mugshot is following you online, our free, confidential consultation will map the footprint and lay out an honest plan.