Papers › Making Images Real Again: A Comprehensive Survey on Deep Image Composition

Making Images Real Again: A Comprehensive Survey on Deep Image Composition

28 Jun 2021arXiv:2106.14490archive 2025-07-28

Li Niu, Wenyan Cong, Liu Liu, Yan Hong, Bo Zhang, Jing Liang, Liqing Zhang

As a common image editing operation, image composition (object insertion) aims to combine the foreground from one image and another background image, resulting in a composite image. However, there are many issues that could make the composite images unrealistic. These issues can be summarized as the inconsistency between foreground and background, which includes appearance inconsistency (e.g., incompatible illumination), geometry inconsistency (e.g., unreasonable size), and semantic inconsistency (e.g., mismatched semantic context). Image composition task could be decomposed into multiple sub-tasks, in which each sub-task targets at one or more issues. Specifically, object placement aims to find reasonable scale, location, and shape for the foreground. Image blending aims to address the unnatural boundary between foreground and background. Image harmonization aims to adjust the illumination statistics of foreground. Shadow (resp., reflection) generation aims to generate plausible shadow (resp., reflection) for the foreground. These sub-tasks can be executed sequentially or parallelly to acquire realistic composite images. To the best of our knowledge, there is no previous survey on image composition (object insertion). In this paper, we conduct comprehensive survey over the sub-tasks and combinatorial task of image composition (object insertion). For each one, we summarize the existing methods, available datasets, and common evaluation metrics. We have also contributed the first image composition toolbox libcom, which assembles 10+ image composition related functions.

PaperPDFCodeCode 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 15 code samples: 13 from 2 repositories linked to this paper, 2 identical to code harvested from another paper's repository. Across all 15: 10 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 1 honoured, 1 violated, 7 with no contract checked; 1 where Syntology's instrument failed) · 5 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

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

No sample is linked to this paper from 2 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 2 of the 10 samples that ran have no recorded date.

bcmi/Awesome-Image-Composition officialmentioned in papermentioned on GitHubSyntology: not harvested report
bcmi/awesome-object-insertion officialmentioned in papermentioned on GitHubSyntology: not harvested report
bcmi/libcom officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 12 samples, 7 ran (0 instrument-failed) · 5 unverified report
bcmi/ObjectStitch-Image-Composition mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
bcmi/controlcom-image-composition mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to ControlCom: Controllable Image Composition using Diffusion Model (arXiv:2308.10040; that paper's own run record: 14 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 6 violated, 0 with no contract checked; 7 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
bcmi/mureobjectstitch-image-composition mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to MureObjectStitch: Multi-reference Image Composition (arXiv:2411.07462; that paper's own run record: 12 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 5 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

15 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 1 honoured, 1 violated, 7 with no contract checked; 1 where Syntology's instrument failed) · 5 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 · honoured contract
1ran · violated contract
1ran · our draft was wrong
7ran
5unverified

Licence: 3 of the 15 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. 2 samples are listed last, in a group without a repository. “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.

bcmi/libcom official repository 12 samples, 7 ran (0 instrument-failed) · 5 unverified
binary_classifier libcom/fos_score/source/networks.py ran Apache-2.0 (permissive) · bbbe8d9d4e08bd78 · report fixture: signature in_ch:int/0/int · returned Sequential · level recorded 2026-09-25
conv_relu_x2 libcom/fos_score/source/networks.py ran Apache-2.0 (permissive) · 8a6243cd7c50b377 · report fixture: signature in_ch:int/0/int, out_ch:int/0/int · returned Sequential · level recorded 2026-09-25
custom_kl_loss libcom/fos_score/source/loss_function.py ran fingerprinted Apache-2.0 (permissive) · 1071f8dab5fd3248 · report fixture: signature p_mu:Tensor/2/float, p_var:Tensor/2/float, q_mu:Tensor/2/float, q_var:Tensor/2/float · returned Tensor · level recorded 2026-09-25
download_entire_folder libcom/utils/model_download.py ran Apache-2.0 (permissive) · c4921cc4e93b1490 · report fixture: signature folder_path:str/0/str · returned str · level recorded 2026-09-26
kl_divergence_loss libcom/fos_score/source/loss_function.py ran fingerprinted Apache-2.0 (permissive) · c548e9c1b67153a9 · report fixture: signature log_var:Tensor/2/float, mu:Tensor/2/float · returned Tensor · level recorded 2026-09-25
mask_iou_loss libcom/fos_score/source/loss_function.py ran fingerprinted Apache-2.0 (permissive) · a0cbbe6df7f2b9d1 · report fixture: signature inputs:Tensor/3/float, targets:Tensor/3/float · returned Tensor · level recorded 2026-09-25
reinhard libcom/color_transfer/reinhard.py ran Apache-2.0 (permissive) · afc884a2a95172a8 · report fixture: signature comp_img:ndarray/3/int, comp_mask:ndarray/2/int · returned ndarray · level recorded 2026-09-25
color_transfer libcom/color_transfer/reinhard.py unverified Apache-2.0 (permissive) · 892e3fedcdabebd6 · report
download_pretrained_model libcom/utils/model_download.py unverified Apache-2.0 (permissive) · cca242a41d647f71 · report
fill_box_with_specified_pixel libcom/fos_score/fos_score_prediction.py unverified Apache-2.0 (permissive) · f15b5e79d5612ae4 · report
get_distillation_module libcom/fos_score/source/networks.py unverified Apache-2.0 (permissive) · ed39e42e5a7eb3b3 · report
padding_to_square libcom/fos_score/fos_score_prediction.py unverified Apache-2.0 (permissive) · bc8e3ebc8aaebb10 · report
bcmi/ObjectStitch-Image-Composition community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
clip2sd scripts/inference.py ran · honoured contract fingerprinted no licence file found · pointer only · 3e5f67215d50b497 · report fixture: signature x:Tensor/4/float · returned Tensor · level recorded 2026-09-22
Repository not located 2 samples, 2 ran (1 instrument-failed) · 0 unverified
2 samples are identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
chunk in 52 papers repository not located ran · our draft was wrong licence of this copy not recorded · 8241c0562bc710fd · report fixture: signature it:list/1/int, size:int/0/int · returned callable_iterator · level recorded, date not recorded
numpy_to_pil in 37 papers repository not located ran · violated contract licence of this copy not recorded · 1e63d588563eb90a · report fixture: signature images:ndarray/4/float · returned list · level recorded, date not recorded

Tasks

Image HarmonizationObjectSurvey

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