
DLD transfer-fee schedules: 18 to 28 September 2026 version check
Disclaimer: This article is for general informational purposes only. It is based on cited public data and published under Lida Moghaddam's RERA-licensed masthead. It is not financial, legal, or investment advice. Dubai's property market moves quickly, so figures, yields, and rules may change or become outdated by the time you read this. Verify current information with the relevant authority or a qualified professional before acting. Read the full disclaimer.
Table of contents+
Across access-dated captures made on 18 and 28 September 2026, all 33 fee-field positions returned across the Dubai Land Department's ordinary Property Sale Registration route and Registering the Sale of a Mortgaged Property route were unchanged: 33 unchanged, 0 changed and 0 newly present. The two routes still publish different field sets, so they should not be collapsed into one DLD fee schedule.
The 10-day comparison found no returned-field change
Every present fee field matched its earlier value. The code compared 28 declared keys for each route across 10 elapsed days. A field marked absent was not returned by that route in either capture. Newly present means it was absent on 18 September and present on 28 September. Changed means a previously returned string differed or disappeared.
The absent counts are not missing money. They show that the fixed union schema contains fields published by the other route. This makes absence visible without filling it by inference.

The ordinary sale page kept 10 returned fee fields unchanged
The ordinary route still separates the seller and buyer percentages. It does not return a total-sale field in the captured fee block, so this tracker preserves the two percentages rather than creating a new source field.
These are returned fields for one service route. The practical Dubai property registration-fee guide explains where these lines sit in a broader purchase file, but that does not turn every property-related charge into part of this page's fee block.
The mortgaged-sale page kept its release, sale and possible mortgage lines unchanged
The mortgaged-property route is a different DLD service record. Its fee block contains mortgage-release lines, sale-stage lines, possible mortgage-stage lines and an exemption note. Each remains at the stage and wording returned by that page.
The final note remains route-specific. It says registrar fees are exempted when a mortgage is registered on the same day, while a next-day case attracts an AED 4,000 plus VAT service-partner line (DLD, accessed 28 September 2026). The tracker records the note. It does not extend it to the ordinary sale route.
The two routes do not publish one interchangeable schedule
The clearest differences are differences in record structure. The ordinary route publishes seller and buyer shares. The mortgaged route publishes a total sale percentage plus release and possible mortgage lines.
The AED 2,000 plus VAT ordinary-route line and AED 2,100 mortgaged-route line are not treated as the same field. Nor are AED 4,000 plus VAT and AED 4,200. The pages give them different route labels, so the tracker keeps them distinct.
How the two captures were compared
The method is simple: preserve each route separately, declare the union of comparison keys before calculating states, then compare exact returned strings. Returned values stay separate from calculated counts.
Capture each route
Save the official fee block with its access date and source URL. Do not use a site-wide footer as the page's revision date.
Declare the keys
Use the same 28 keys for each route. A route-specific field can then be present, absent, changed or newly present without being mapped onto a different service line.
Compare exact strings
The comparison tests the 18 and 28 September values as exact strings and checks each normalized fee block with SHA-256.
Audit every returned field
The comparison covers all 33 current-present fields, including each earlier value, current value, state, service route and official URL.
This record proves stability between captures, not a universal version history
The evidence supports one narrow conclusion: the declared fee fields on these two DLD service pages did not change between the captures accessed on 18 and 28 September 2026. It does not prove that no field changed before, after or between those reads.
It also does not convert route wording into market practice. A page field is evidence of what that service page returned. Contract allocations, trustee handling and a reader's transaction file require their own records.
The site footer is excluded because it applies across the DLD website. Neither named page exposes a page-specific fee-schedule version identifier or revision date. Until one appears, the honest version label is the access date.
What is the property transfer fee in Dubai?
How much is the title deed fee?
Both named pages returned an AED 250 title-deed line, but the route and stage remain part of the record (ordinary sale and mortgaged sale, accessed 28 September 2026).
What are DLD charges in Dubai?
They depend on the service route. These two captures include sale percentages, maps, title deeds and route-specific registrar, partner, release or possible mortgage lines (DLD ordinary sale and DLD mortgaged sale, accessed 28 September 2026).
Who pays the 4% DLD fee in Dubai?
How can a DLD fee change be verified?
Use immutable captures of the same official service route, a declared comparison key set and explicit states for unchanged, changed, absent and newly present fields. Record access dates when the page supplies no page-specific revision date.
Architect-turned-real-estate-specialist based in Dubai. She helps buyers, sellers, and investors read property with a designer's eye — structure, location, and long-term value.













