Papers › Detecting Photoshopped Faces by Scripting Photoshop

Detecting Photoshopped Faces by Scripting Photoshop

13 Jun 2019ICCV 2019 10arXiv:1906.05856archive 2025-07-28

Sheng-Yu Wang, Oliver Wang, Andrew Owens, Richard Zhang, Alexei A. Efros

Most malicious photo manipulations are created using standard image editing tools, such as Adobe Photoshop. We present a method for detecting one very popular Photoshop manipulation -- image warping applied to human faces -- using a model trained entirely using fake images that were automatically generated by scripting Photoshop itself. We show that our model outperforms humans at the task of recognizing manipulated images, can predict the specific location of edits, and in some cases can be used to "undo" a manipulation to reconstruct the original, unedited image. We demonstrate that the system can be successfully applied to real, artist-created image manipulations.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 10 code samples harvested from 1 repository linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 1 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 10 samples from 1 repository, 7 ran (6 with no instrument failure; 1 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

PeterWang512/FALdetector mentioned on GitHubpytorchApache-2.0Syntology: 10 samples, 7 ran (1 instrument-failed) · 3 unverified report
phixion/phixion mentioned on GitHubpytorchSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

10 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 1 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
6ran
3unverified

Licence: 1 of the 10 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from PeterWang512/FALdetector. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

PeterWang512/FALdetector community (archive-listed) 10 samples, 7 ran (1 instrument-failed) · 3 unverified
center_crop in 48 papers utils/tools.py ran Apache-2.0 (permissive) · c4019770f99361ad · report fixture: signature im:Image/0/?, length:int/0/int · returned tuple · level recorded 2026-09-24
conv3x3 in 1,376 papers networks/drn.py ran · our draft was wrong Apache-2.0 (permissive) · 0e722c9ff0920473 · report fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int, padding:int/0/int, dilation:int/0/int · returned Conv2d · level recorded 2026-09-22
drn_a_50 networks/drn.py ran Apache-2.0 (permissive) · 19e291fafc7bb35b · report fixture: signature pretrained:bool/0/bool · returned DRN_A · level recorded 2026-09-25
get_heatmap_batch utils/visualize.py ran fingerprinted Apache-2.0 (permissive) · 7b3fe2745271414b · report fixture: signature img_batch:Tensor/4/float, pred_batch:Tensor/4/float · returned Tensor · level recorded 2026-09-24
remove_boundary utils/tools.py ran Apache-2.0 (permissive) · 31f27cfaf2e17176 · report fixture: signature img:Image/0/? · returned Image · level recorded 2026-09-24
resize_shorter_side utils/tools.py ran Apache-2.0 (permissive) · 910e8701c0ed21ba · report fixture: signature img:Image/0/?, min_length:int/0/int · returned tuple · level recorded 2026-09-24
unnormalize in 21 papers utils/visualize.py ran Apache-2.0 (permissive) here; the stored copy is pointer only · 7742460f647f9ca2 · report fixture: signature tens:Tensor/4/float, mean:list/1/float, std:list/1/float · returned Tensor · level recorded 2026-09-25
classify_fake global_classifier.py unverified Apache-2.0 (permissive) · a6a09be2fd8eb095 · report
drn_c_26 networks/drn.py unverified Apache-2.0 (permissive) · f2cb2c00d5b19823 · report
get_heatmap_cv utils/visualize.py unverified Apache-2.0 (permissive) · 40e586b15242d87d · report

Tasks

Image Manipulation Detection

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections