Is Scraping Zillow Legal? (Terms of Use & What's Allowed)

I have built Zillow data pipelines for years, and the first question every client asks is whether scraping Zillow is even allowed. So I did the unglamorous work: I read Zillow’s current Terms of Use line by line, pulled its robots.txt, and went through the scraping case law that actually governs this in the US. The short version is that “is scraping Zillow legal” has a different answer depending on whether you mean federal criminal law, Zillow’s contract, copyright, or privacy. They do not all point the same way.

Below I separate what is legal, what merely breaks Zillow’s rules, and what can land you in court, with the primary sources for each.

Is scraping Zillow legal?

Scraping publicly visible Zillow data is generally legal in the United States, in the narrow sense that it does not violate the federal Computer Fraud and Abuse Act (CFAA). The Ninth Circuit Court of Appeals settled the core question in hiQ Labs v. LinkedIn, holding that automated scraping of publicly accessible web pages does not count as accessing a computer “without authorization.” Public data is, in the court’s framing, already open to anyone with a browser.

That ruling is the reason so many people say scraping Zillow is “perfectly legal.” It is half the picture. The CFAA is a criminal anti-hacking statute, and clearing it only means you are not committing a federal computer crime by reading public pages. It says nothing about Zillow’s contract with you, the copyright in Zillow’s compiled database, or the privacy laws that attach to personal data.

So the accurate framing for 2026 is layered. Reading public listing pages with an automated client is lawful at the federal-access level, but doing it in defiance of Zillow’s Terms of Use is a contract breach, copying Zillow’s structured data in volume can infringe copyright, and the moment you collect agent names, phone numbers, or other personal details, privacy statutes enter the room. The next sections take each layer in turn, starting with what Zillow itself permits.

Does Zillow allow web scraping?

Zillow does not allow web scraping. Its Terms of Use, updated October 28, 2025, prohibit automated access in a dedicated Prohibited Use section. The relevant clause bars users from conducting “automated queries (including screen and database scraping, spiders, robots, crawlers, bypassing ‘captcha’ or similar precautions, or any other automated activity with the purpose of obtaining information from the Services).”

That language is about as explicit as a scraping prohibition gets. Zillow calls out screen scraping, database scraping, spiders, robots, crawlers, and CAPTCHA bypass by name. The Zillow terms of use scraping prohibition applies to automated access regardless of whether the use is personal or commercial.

There is one narrow carve-out worth knowing. Zillow’s terms permit you to copy listing information “without the aid of any automated processes and only as necessary for your personal use.” In plain terms, you can manually open a listing and save it for yourself. The instant you point a script, bot, or crawler at the site, you are outside that permission and inside the prohibited-use clause.

Here is how the policy breaks down against common assumptions:

A Terms of Use prohibition is a contract term. It does not carry the force of a statute, so breaking it does not make scraping a crime by itself, a distinction I cover in the legal-risk section below. Before that, it helps to see what Zillow signals to automated clients through a different channel: its robots.txt.

What does Zillow’s robots.txt say about scraping?

Zillow’s robots.txt sets crawler rules that allow indexing of a small set of public listing paths and disallow large sections of the site. For the default user-agent, Zillow allows top-level pages such as /homes/for_sale/, /homes/for_rent/, and /homes/recently_sold/ along with their paginated variants, while disallowing broad areas including /api/, /graphql/, most /homes/ detail-page variants, /myzillow/, /user/, /mobile/, and various /ajax/ endpoints.

The file also addresses specific bots. Social crawlers like facebookexternalhit, LinkedInBot, and Twitterbot get their own rules. Several AI and research crawlers, including Amazonbot, Applebot-Extended, meta-externalagent, and AI2Bot, are named and given a Crawl-delay: 1, and a few bots such as ActiveComplyBot, CriteoBot, and GumGumBot are blocked outright.

The Zillow robots.txt scraping policy is a request for crawler etiquette. robots.txt is a voluntary standard from the 1990s that well-behaved search crawlers honor; it does not carry the force of law, and ignoring it is not itself a crime. What it does provide is evidence: if a dispute reaches court, a Disallow directive that you knowingly ignored helps show you understood Zillow did not consent to automated access, which strengthens a breach-of-contract or trespass argument. So robots.txt matters mainly for risk exposure, and it does not decide legality on its own.

That distinction, between what is technically against the rules and what is actually unlawful, is exactly where most confusion lives. The next section addresses it directly.

Is scraping Zillow illegal, or just against the rules?

Scraping Zillow is against Zillow’s rules but is generally not illegal under US federal law when you collect only public data. The gap between “prohibited” and “illegal” is the single most important thing to understand about Zillow scraping, and it comes down to which body of law you are asking about.

US courts have steadily narrowed the criminal statute most often raised against scrapers. In hiQ Labs v. LinkedIn, the Ninth Circuit held that scraping publicly accessible pages does not violate the CFAA’s bar on access “without authorization.” The Supreme Court then narrowed the CFAA further in Van Buren v. United States (decided June 3, 2021), ruling that a person “exceeds authorized access” only by reaching areas of a computer that are off-limits to them. Misusing data you were already entitled to view falls outside the statute. Together these decisions mean that reading Zillow’s public listing pages is very unlikely to be a federal computer crime.

Contract law is the live exposure. In Meta Platforms v. Bright Data, Judge Edward Chen granted summary judgment for the scraper on January 23, 2024, finding that Bright Data did not breach Facebook’s and Instagram’s terms by scraping while logged out, since the terms it agreed to applied to logged-in use. The lesson for Zillow is specific: whether scraping breaches a site’s contract turns on the exact terms and whether you were logged in or bound by them when you collected the data. Zillow’s prohibition is broad and not limited to logged-in users, so the contract risk on Zillow is higher than it was for the logged-out scraping in the Bright Data case.

This table maps the question to the law that answers it:

The takeaway is that “is scraping Zillow illegal” is the wrong single question. The CFAA answer is mostly no. The contract answer is yes. The copyright and privacy answers are “it depends on what you take.” That brings us to the concrete consequences.

What are the legal consequences of scraping Zillow?

The legal consequences of scraping Zillow without permission are civil in the typical case, and they fall into three buckets: account and IP bans, breach-of-contract claims, and copyright or privacy claims tied to what you collected.

The first consequence is enforcement that never reaches a courtroom. Zillow runs anti-bot defenses, so the most common outcome is a block: IP bans, CAPTCHA challenges, and rate limits that cut off automated traffic. Zillow can also terminate any account associated with the activity. This is contract enforcement by technical means, and it is the result the overwhelming majority of scrapers actually experience.

The second consequence is a breach-of-contract claim. Because Zillow’s Terms of Use prohibit automated access, large-scale scraping in defiance of those terms can expose you to a civil suit for breach. Remedies can include injunctions ordering you to stop and, where the site can show harm, monetary damages. The hiQ litigation is the cautionary tail end here: hiQ won on the CFAA but the dispute over LinkedIn’s User Agreement continued, and in late 2022 the case resolved with hiQ on the losing side of the contract question before settling. Winning the criminal-statute argument did not end the contract liability.

The third consequence attaches to the content of what you scrape. Two areas carry the most exposure:

• Copyright on compiled data. Individual facts like a price or square footage are not copyrightable, but a substantial copy of Zillow’s selected, arranged, and compiled database can infringe Zillow’s copyright in that compilation. Bulk reproduction is riskier than reading a handful of listings.
• Personal data. Listing pages and agent profiles contain names, phone numbers, and other identifiers. Collecting those pulls you under privacy statutes such as the CCPA in California and the GDPR for EU residents, each with its own obligations and penalties.

The single biggest variable is whether you touch personal data. That deserves its own section, because it changes the analysis entirely.

Does privacy law apply when scraping Zillow agent or contact data?

Privacy law applies the moment you scrape personal data from Zillow, such as agent names, phone numbers, email addresses, or any detail that identifies a specific person. Scraping anonymous price and property facts is one risk profile. Scraping people is a much higher one, and the “it is public” defense is weaker than most people expect.

Under California’s CCPA, the “publicly available” exemption is narrow. Information only escapes the definition of personal information when it is lawfully obtained from government records and used for a compatible purpose. Data that is merely visible on a website does not automatically qualify, so scraped agent contact details can still be regulated personal information with disclosure and deletion obligations attached.

The European GDPR is stricter still. It applies to the personal data of people in the EU regardless of where the scraper operates, and it requires a lawful basis for processing. There is no blanket “public data is free” rule. If your scrape sweeps up any EU agents or consumers, you inherit GDPR duties around purpose, consent or legitimate interest, and data-subject rights.

US real-estate data carries an extra trap. If you use scraped Zillow information to help make decisions about a consumer’s eligibility for housing, credit, insurance, or employment, you can fall under the federal Fair Credit Reporting Act (FCRA), which the FTC enforces. Lead-generation and tenant-screening uses are where this bites. The compliance burden of personal data is the strongest argument for limiting what you collect, and for choosing a sanctioned data route where one exists. Those routes are the final piece.

What are the legal alternatives for getting Zillow data in 2026?

The legal alternatives for getting Zillow data in 2026 are Zillow’s own research downloads, its licensed API for approved partners, and a scraper API that collects only public listing pages. Each fits a different need, and picking the right one is mostly about volume and whether you need live listings or aggregate trends.

Zillow’s research data is the cleanest option for market analysis. Zillow publishes the Zillow Home Value Index (ZHVI) and Zillow Observed Rent Index (ZORI) as free downloads for public use by consumers, media, analysts, and academics, with attribution required. When you need housing trends and can work without individual live listings, this is sanctioned and free. I walk through these files in my guide to Zillow research data, ZHVI and ZORI, and it is worth knowing the ATTOM, MLS, and GreatSchools sources behind Zillow’s data so you can judge what the downloads cover.

Zillow’s licensed API is the route for sanctioned programmatic access. Per Zillow’s developer terms, the API is open to “preapproved licensees” who hold a Zillow-issued identifier and follow branding, call-limit, and no-resale requirements. This is the compliant path if you can get approved, though approval and the resale restrictions rule it out for many commercial data projects.

A scraper API is the option most teams reach for when they need live public listings at scale without operating proxies or fighting CAPTCHAs themselves. The model is simple: you send a public Zillow URL and receive parsed JSON, with the blocking handled server-side. Shaped like Zillow’s own pages, a request looks like this:

curl "https://chocodata.com/api/v1/zillow/property?url=https://www.zillow.com/homedetails/2092-zpid/&api_key=$CHOCO_API_KEY"

This pulls a single public property page. The same pattern extends to the data most projects actually want: a Zillow listings and property scraper for for-sale and sold inventory, a Zillow rental data API for rent prices, and a Zillow home price and sales API for valuation history. Because these requests hit only public pages, they stay on the right side of the CFAA line that hiQ drew, while leaving Zillow’s Terms-of-Use prohibition in play exactly as it would be for any scraper. You can compare the managed options in my roundup of the best Zillow scrapers and APIs.

Here is how the three routes compare:

The honest summary is that no route is risk-free if you need live listing data at volume, because Zillow’s terms prohibit automated collection regardless of the tool. What changes across these options is the legal exposure on personal data and copyright, the engineering burden, and how quickly you get blocked. For aggregate trends, the research downloads remove the question entirely. For live data, a scraper API that touches only public pages is the pragmatic middle ground, and you can start one at ChocoData.