null Skip to main content

DPF 510GTRX - 3.2 mil Gloss White Cal, Tinted removable PSA, Air-Egress

$229.95 - $257.95
Financing Options:

DPF 510GTRX

DPF 510GTRX offers exceptional print quality at an incredible value for your short-term projects. With X-Scape Technology®, it ensures a bubble-free installation and a smooth, paint-like finish, making it ideal for promotional graphics and beyond. This film provides uniform ink receptivity across most printing systems, resulting in vibrant, high-quality graphics. Its light gray, cleaning removing adhesive facilitates easy application while providing sufficient opacity to cover existing graphics. For enhanced abrasion resistance, pair DPF 510GTRX with Series 3510 overlaminate. DPF510GTRX is rated for outdoor durability up to 3 years (unprinted). Printed durability is dependent on the ink system used.

Recommended Applications

  • Short-Term Interior or Exterior Signage
  • POP / Trade Show Graphics
  • Decals

Recommended Overlaminate

  • Series 3510

Unique Features

  • Low Profile X-Scape Technology® for Easy, Bubble-Free Installations
  • Cleaning Removing Adhesive
  • Exceptional, Vibrant Print
  • Consistent Performance with High Heat Printers
  • Certified to ASTM E 84 Class A

Face Film Thickness

  • 2-Mil

Finish

  • Gloss

Adhesive

  • Removable (Tinted)

Release Liner

  • Lay-Flat Polycoated with Low Profile X-Scape Technology®

Durability (Unprinted)

  • 3 Years

Ink Compatibility

  • Eco-Solvent
  • Solvent
  • UV
  • Latex

 

// Uses React's native (unpatched) value setter + a real dispatched event, // so the app's own onChange / validation / append logic fires correctly. // build the visible field the user will actually type into // copy the real field's classes + computed styles so it looks identical // preload with existing value (formatted) if the real field already has one // hide the real field visually but keep it in the DOM and functional, // so your app's own validation / append event still works as before // place the visible field right where the real one used to be // send only the plain digits to the real field — this matches what // the numeric field type expects, so no "invalid phone number" error // keep focus/blur events flowing to the real field too, in case your // app's validation triggers specifically on those