Methods › General › Loss Functions › VGG Loss

VGG Loss

37 papers tagged archive 2025-07-28

Introduced by Christian Ledig et al. in Photo-Realistic Single Image Super-Resolution Using a Generative Adversarial Network

archive 2025-07-28 Description, source and code snippet are the archive's method entry.

VGG Loss is a type of content loss introduced in the Perceptual Losses for Real-Time Style Transfer and Super-Resolution super-resolution and style transfer framework. It is an alternative to pixel-wise losses; VGG Loss attempts to be closer to perceptual similarity. The VGG loss is based on the ReLU activation layers of the pre-trained 19 layer VGG network. With ϕ_(i,j) we indicate the feature map obtained by the j-th convolution (after activation) before the i-th maxpooling layer within the VGG19 network, which we consider given. We then define the VGG loss as the euclidean distance between the feature representations of a reconstructed image G_(θ_G)(Iᴸᴿ) and the reference image Iᴴᴿ:

l_(VGG/i.j) = 1/(W_(i,j)H_(i,j))∑ₓ₌₁^(W_(i,j))∑_(y=1)^(H_(i,j))(ϕ_(i,j)(Iᴴᴿ)_(x, y) - ϕ_(i,j)(G_(θ_G)(Iᴸᴿ))_(x, y))²

Here W_(i,j) and H_(i,j) describe the dimensions of the respective feature maps within the VGG network.

PaperSourceSee Code · tensorlayer/srgan

In Syntology name not resolved (unknown_name). The lookup matched no method, paper or venue by this name; that asserts nothing about whether code exists.

Near matches the lookup lists, each a different name: VGG-Flow; RepOpt-VGG; VGG-MADiffRL.

Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.

Papers archive 2025-07-28

archive papers tagged: 37 · with a code link: 17 · where Syntology ran a sample: 4 (4 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (4 of 37 tagged: 4 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)

Page 1 of 1: papers 1 to 37 of 37, newest first by the archive's date (ties by slug), in archive order.

Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.

Tasks archive 2025-07-28

20 shown of 41 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.

TaskPapers
Super-Resolution34
Image Super-Resolution23
Generative Adversarial Network14
SSIM8
Quantization2
Video Super-Resolution2
Brain Tumor Segmentation1
CPU1
Data Compression1
Deep Learning1
Denoising1
Diversity1
Domain Adaptation1
Edge Detection1
Face Hallucination1
GPU1
Image Classification1
Image Compression1
Image Enhancement1
Image Generation1

Usage over time archive 2025-07-28

Papers per year tagged with VGG Loss: 2016 to 2025, peak 9 9 0 2016: 1 paper 2016 2017: 0 papers 2017 2018: 6 papers 2018 2019: 6 papers 2019 2020: 9 papers 2020 2021: 3 papers 2021 2022: 4 papers 2022 2023: 3 papers 2023 2024: 4 papers 2024 2025: 1 paper 2025
Papers per year the archive tags with this method, by the paper's archive date (37 dated). Bars are counts, not a trend claim.

Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).

Categories archive 2025-07-28

Loss Functions

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