- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2(+1)
Read review
Paper summary
This paper proposes a self-embedding fragile watermarking method that leverages DWT frequency information as a redundancy watermark for image tampering recovery. The framework consists of three main stages: (1) RHWG: Creates a "raw" watermark by separating the image into low-frequency (Base) and high-frequency (Enhancement) components. (2) CAWE: Utilizes two U-Net networks to process the original image alongside the backup features, generating a watermark modulation signal "R" that is subsequently added to the original image. (3) RMBR: Extracts the watermark, reverses the rearrangement, and localizes the manipulated regions.
Critical strengths
- The experimental section is a key strength of this work. The proposed method demonstrates consistent, system-level performance gains across multiple datasets and various manipulation types.
Critical weaknesses
- While the proposed architecture is technically sound and plausible, the overall conceptual novelty remains unclear. The framework appears to combine several established techniques and ideas without sufficient differentiation from existing literature: (1) Classic works such as Fridrich & Goljan [1] and Zhang et al. [2] have already extensively discussed self-embedding, image derived references across regions for recovery, and multi-region partitioning for image recovery. (2) Even compared to the references cited within the manuscript, the framework shares substantial similarities with "RelImage," which already embeds shuffled image information and refines the recovery process using enhancement.
[1] Fridrich & Goljan, “Images with Self-Correcting Capabilities,” ICIP 1999 [2] Zhang, Wang, Qian & Feng, “Reference Sharing Mechanism for Watermark Self-Embedding,” IEEE TIP 2010
Questions for authors
-
Are the baseline comparisons conducted at a comparable parameter scale? For instance, Table 7 indicates that ProCast uses 194M parameters, whereas RelImage uses 9.94M parameters. While this does not invalidate the observed performance gains, it remains unclear how much of the improvement comes from the core methodology rather than a significantly larger network capacity and different optimization dynamics.
-
Tables 4 and 5 indicate that the Base+Enhancement configuration yields an improvement of approximately 0.3 dB, while the majority of the system gain appears to derive from the embedding and fusion stages. Given these results, does the learned hierarchy provide a distinct advantage, or does the system primarily benefit from a compact reconstruction representation paired with embedding and fusion? The claimed contribution regarding "learning what to protect" requires further clarity in light of these ablation results.
-
Several design choices appear arbitrary and require further justification. For example, (1) In the RMBR module, the two decoded views share the same enhancement. Does this imply that any corruption of the enhancement component will simultaneously degrade both views? (2) The locator module mixes spatial information. Will extraction errors potentially affect a broader area than the directly manipulated carrier region? (3) While the OACB reversible construction is mathematically motivated, the rationale for its architecture and protection allocation is quite limited.
-
The loss functions fundamentally define the operations of the "Base," "Enhancement," and "Auxiliary" components. However, the explicit training loss computations are put to the Appendix. Since these losses serve as foundational support for the method, it is recommended to move this discussion into the main text.
5 comments
Rebuttal by Authors (2/3)
Table R6. Capacity-scaling and parameter-efficiency comparison under the same evaluation protocol.
| Model | Extractor | Params | WM PSNR↑ | Rec. PSNR↑ |
|---|---|---|---|---|
| SSEM-HIR | — | 200M | 28.83 | 27.30 |
| ReImage | — | 9.9M | 37.07 | 30.81 |
| ReImage-Large | — | 72.59M | 33.97 | 31.30 |
| ProCast-Tiny | ConvNeXt-Tiny | 74M | 41.30 | 34.19 |
| ProCast | ConvNeXt-Base | 194M | 41.95 | 35.50 |
A2:Tables 4 and 5indicate that the Base+Enhancement configuration yields an improvement of approximately 0.3 dB, while the majority of the system gain appears to derive from the embedding and fusion stages. Given these results, does the learned hierarchy provide a distinct advantage, or does the system primarily benefit from a compact reconstruction representation paired with embedding and fusion? The claimed contribution regarding "learning what to protect" requires further clarity in light of these ablation results.
A2: Thanks for your question. We conducted additional ablation experiments to further demonstrate the contribution and effectiveness of role-aware learning (Table 5).
- A(2.1): Clarification of
Table 4. The PSNR in Table 4 is an encoder-side component reconstruction metric. For each combination, the selected components are directly passed to the decoder, while the remaining components are set to zero. Therefore, no watermark embedding, manipulation, extraction, or backup fusion is involved. It can not reflect the gain that appears to derive from the embedding and fusion stages. Therefore, the approximately 0.3 dB difference in Base+Enhancement reconstruction does not imply that the performance gains come from embedding or fusion. To avoid further confusion, we have clarified this evaluation procedure in both the caption ofTable 4and the revised manuscript (page 10). - A(2.2): Does role-aware learning effectively learn what information should be protected for recovery
Table 4is intended to verify whether role-aware learning successfully identifies which information is essential for recovery. With the same representation capacity, Base + Enhancement achieves similar reconstruction quality with and without role-aware learning (25.199 vs. 24.879 dB). However, the key difference lies in how recovery information is distributed. Without role-aware learning, adding Enhancement improves PSNR by 6.911 dB (17.968 → 24.879 dB). With role-aware learning, Base alone achieves 24.816 dB, while Enhancement contributes only an additional 0.383 dB. These results demonstrate that role-aware learning concentrates the primary recovery information in Base rather than simply increasing reconstruction capacity. - A(2.3): Contribution of role-aware learning. We extended Table 5 with an RHWG end-to-end ablation. We removed role-aware learning while keeping the same backup allocation (B×2+E), payload size (34,560), and all other settings unchanged. The full model achieves comparable WM PSNR, while improving Ref. PSNR by 4.406 dB and Rec. PSNR by 4.358 dB . These results demonstrate that, under the same payload size, role-aware learning improves recovery fidelity without compromising watermark imperceptibility.
Table 5. Ablation study of the key designs in RHWG, CAWE, and RMBR.
Module Ablation Setting WM PSNR Ref. PSNR Rec. PSNR RHWG w/o Role-aware learning 40.309 20.496 30.196 CAWE Fixed subband 38.744 23.367 32.482 RMBR Average fusion 40.002 21.542 30.698 ProCast Full 40.601 24.902 34.554
Rebuttal by Authors (3/3)
Q3.1: In the RMBR module, the two decoded views share the same enhancement. Does this imply that any corruption of the enhancement component will simultaneously degrade both views?
A(3.1): Yes. Enhancement's corruption may affect both decoded views. However, this is precisely why we introduce role-aware learning and unequal protection. In our design, Base is trained to retain the primary recovery information, and Enhancement carries only less complementary information. Thus, even if Enhancement is corrupted, the main content can still be recovered from Base backup. Table 4 supports this design. Without role-aware learning, Enhancement carries important recovery information (Base → Base+Enhancement: ↑6.911 dB). With role-aware learning, its contribution becomes much smaller (↑0.383 dB). At the system level, Table 5 further shows that, under the same payload and (B×2+E) allocation, role-aware learning improves Ref. PSNR from 20.496 to 24.902 dB. This supports the effectiveness of aligning information roles with unequal protection. The recovery-critical information is concentrated in the duplicated Base, while the single-copy Enhancement is used only for refinement.
Q3.2: The locator module mixes spatial information. Will extraction errors potentially affect a broader area than the directly manipulated carrier region?
A(3.2): Local extraction errors may affect neighbouring features because the extractor and Locator use spatial context. However, this does not necessarily lead to errors spreading across the predicted localization mask. We have considered this issue in our design. Specifically, the Locator uses the pixel-aligned discrepancy () to identify local inconsistencies between the received image and the extracted reference. Together with pixel-level BCE and Dice supervision, this helps limit the spread of localization errors. Across three general image manipulation scenarios, ProCast achieves an average F1 of 0.9892, AUC of 0.9996, and IoU of 0.9805, suggesting that spatial spreading of localization errors is limited in practice.
Q3.3: While the OACB reversible construction is mathematically motivated, the rationale for its architecture and protection allocation is quite limited.
A(3.3): OACB and the subsequent protection allocation address two different requirements. We provide a detailed explanation below.
- OACB architecture. Our objective is not merely to extract compact features, but to learn how recovery information should be redistributed among components with different protection priorities. Conventional non-invertible encoders may lose information during feature extraction, making it difficult to distinguish intentional component allocation from irreversible encoding loss. In contrast, OACB preserves the complete latent representation when all components are retained. Its orthogonal mixing enables information exchange across channels, while additive coupling provides nonlinear learnable transformations with an exact inverse. Consequently, information loss occurs only when components are intentionally omitted, making the learned recovery roles interpretable and compatible with unequal protection.
- Protection allocation. Our protection strategy follows the learned recovery roles of different components. As shown in
Table 4, Base alone achieves 24.816 dB, while Enhancement and Auxiliary provide only small additional gains (↑0.383 dB and ↑0.060 dB). Therefore, we duplicate Base for stronger protection, transmit Enhancement once, and discard Auxiliary to reduce the payload size. This ensures that more important recovery information receives stronger protection.
Q4: Since these losses serve as foundational support for the method, it is recommended to move this discussion into the main text.
A4: We have moved the detailed loss formulations from the Appendix to the main paper (page 5).
Reference
Rebuttal by Authors (1/3)
We sincerely appreciate your constructive comments. We have carefully addressed your concerns and revised the manuscript. We are happy to discuss further concerns you may have.
A1: We apologize for the confusion. Here, we clarify our key conceptual novelty and explain how ProCast differs from and advances beyond R1, R2, and RegImage.
Our key conceptual novelty lies in shifting from predefined recovery representations to learned functional recovery roles that guide the overall self-recovery framework.
A1:: We acknowledge that ProCast (194M) has more parameters than ReImage (9.94M). However, ProCast is not unusually large relative to other recent self-recovery methods, such as SSEM-HIR [1] (200M) and VeriFi [3] (157.12M).
Scale down our ProCast. To directly examine the influence of network capacity, we replaced ConvNeXt-Base with ConvNeXt-Tiny while keeping the remaining architecture unchanged (
Table R6). This reduces the total parameter count from 194M to 74M, while producing only minor changes in WM PSNR and recovery PSNR. More importantly, ProCast-Tiny still outperforms ReImage by 4.23 dB in WM PSNR and 3.38 dB in Rec. PSNR. SSEM-HIR also has slightly more parameters than the full ProCast model but achieves lower performance. These results suggest that performance is not solely determined by model size.Scaling up ReImage. Similarly, we increased the width and depth of ReImage’s existing subnetworks while preserving its overall architecture and core mechanisms. This increased the parameter count from 9.94M to 72.59M, making it comparable in size to ProCast-Tiny (74M). Nevertheless, ProCast-Tiny (74M) still outperforms the scaled-up ReImage-L (72.59M), suggesting that our performance gains are not simply due to increased model capacity.
Table R6is provided in Rebuttal by Authors (2/3)