Shutterfly, Inc. Patent litigation record

Company 12 cases

12 cases on record naming Shutterfly, Inc.: 0 as claimant, 12 as respondent. Each row links to that case’s full docket record.

Litigation indexPatsnap Litigation Data··Docket source: PACER

12 cases on record

Cases on record
12
As claimant
0
As respondent
12
Patents held
Not recorded
Core tech
Not recorded
Case no.PartiesRoleCourtFiledDurationOutcome
2:25-cv-00642 DigiMedia Tech, LLC v. Shutterfly, LLC Defendant E.D. Tex. 17 Jun 2025 160 d Dismissed with Prejudice
1:19-cv-08313 Internet Media Interactive, Corp. v. Shutterfly, Inc. Defendant S.D.N.Y. 6 Sep 2019 48 d Voluntary dismissal
2:16-cv-01053 Plano Encryption Technologies, LLC v. Shutterfly, Inc. Defendant E.D. Tex. 28 Sep 2016 331 d Likely Settlement
9:16-cv-80190 Shipping & Transit, LLC v. Shutterfly, Inc. Defendant S.D. Fla. 5 Feb 2016 6 d Voluntary dismissal
2:15-cv-02046 Opal Run, LLC v. Shutterfly, Inc. Defendant E.D. Tex. 30 Nov 2015 168 d Likely Settlement
5:15-cv-05437 High Quality Printing Inventions, LLC v. Shutterfly, Inc. Defendant N.D. Cal. 25 Nov 2015 106 d Voluntary dismissal
2:15-cv-01743 CryptoPeak Solutions, LLC v. Shutterfly, Inc. Defendant E.D. Tex. 9 Nov 2015 63 d Out-of-court Settlement
1:15-cv-03969 American Needle, Inc. v. Shutterfly, Inc. Defendant N.D. Ill. 5 May 2015 100 d Voluntary dismissal
2015-1383 TLI Communications, LLC v. Shutterfly, Inc. Defendant Fed. Cir. 26 Feb 2015 446 d Closed
1:15-cv-00098 Fo2go, LLC v. Shutterfly, Inc. Defendant D. Del. 27 Jan 2015 269 d Likely Settlement
1:14-cv-00788 TLI Communications, LLC v. Shutterfly, Inc. Defendant E.D. Va. 25 Jun 2014 226 d Other
1:13-cv-00384 CreateAds, LLC v. Shutterfly, Inc. Defendant D. Del. 7 Mar 2013 761 d Likely Settlement
Source: Patsnap Litigation Data. Cases naming Shutterfly, Inc. in the current snapshot. Run this in Eureka
Patsnap Eureka

See what Shutterfly is protecting

Portfolio, claim scope and where its coverage is thin. Every answer cites the records behind it.

Analyse this portfolio
10,000 free credits to start

About this summary. This page summarises the litigation records within the coverage and snapshot dates stated here. Counts describe records in that dataset and do not, by themselves, establish the conduct, litigation success or legal position of any person or organisation.

Docket data has limits. Records are drawn from a snapshot and may lag the live docket. Sealed filings, amended complaints, counterclaims and post-closure motions may not be reflected. Party names, attorney names and firm affiliations are reproduced as recorded and may contain omissions. Where a field is absent from the record, this page marks it as not recorded rather than inferring a value.

No characterisation of the parties or the outcome. This page reports what the record contains. Nothing here should be read as an assertion that any party infringed, that any patent is valid or invalid, that any settlement occurred, or that any party prevailed. The filing of a claim is not a court finding, and a docket marked “closed” does not by itself establish infringement, validity, settlement or a decision on the merits.

No FTO or validity opinion. Nothing on this page constitutes a freedom-to-operate, novelty, validity or infringement opinion. Any decision touching a live patent dispute should be verified independently and reviewed with qualified patent counsel.

Third-party names and marks. Party, attorney, judge and company names appear for identification only. Company names may be trademarks of their owners; their appearance does not, by itself, imply affiliation with or endorsement by Patsnap.

Corrections and privacy requests. To report an inaccurate record or attribution, use the “Report an incorrect record” link on this page. For requests concerning your personal information, including, where applicable, the rights to access, rectify, erase, restrict or object to processing, use the “Privacy request” link. We assess requests under applicable law. See our Privacy Policy for details of this processing.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.